[jira] Commented: (MECLIPSE-408) eclipse:eclipse creates a .classpath containing the M2_REPO variable followed by the expanded value of the variable
[ http://jira.codehaus.org/browse/MECLIPSE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160687#action_160687 ] Neil Crow commented on MECLIPSE-408: I am experiencing this too, and I found a jira for this issue which was closed but I think should be reopened. http://jira.codehaus.org/browse/MECLIPSE-408 my setting: winXP Maven-2.0.9 maven-eclipse-plugin-2.5.14 eclipse-3.4.0 m2eclipse-plugin-0.9.6.20080905-0917 Regards, Neil Crow. See discussion on user mailing list http://www.nabble.com/Mvn-eclipse%3Aeclipse---strange-M2_REPO-settings-tt20541566.html > eclipse:eclipse creates a .classpath containing the M2_REPO variable followed > by the expanded value of the variable > --- > > Key: MECLIPSE-408 > URL: http://jira.codehaus.org/browse/MECLIPSE-408 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Environment: MS Windows XP, + cygwin >Reporter: Gus Mancuso > Attachments: Copy of pom.xml, parentPom.xml, settings.xml > > > Using maven 2.0.8, and eclipse plugin (version 2.4 or 2.5). When I run mvn > eclipse:eclipse the .classpath that gets generated is invalid. My M2_REPO > variable is set to /var/maven and the classpath entries for dependencies look > like : >path="M2_REPO/var/maven/commons-collections/commons-collections/3.1/commons-collections-3.1.jar"/> > where >path="M2_REPO/commons-collections/commons-collections/3.1/commons-collections-3.1.jar"/> > would be the correct entry. > Things about my environment that may be affecting this: > * I run maven from a cygwin bash prompt. > * /var/maven is a symlink to /cygdrive/c/var/maven > * MAVEN_HOME is C:\opt\maven-2.0.8 > settings.xml and pom.xml for the affected project is included. It should be > noted that some other projects on the same machine seem to work fine, but > others dont. I don't see any -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MECLIPSE-408) eclipse:eclipse creates a .classpath containing the M2_REPO variable followed by the expanded value of the variable
[ http://jira.codehaus.org/browse/MECLIPSE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160687#action_160687 ] Neil Crow edited comment on MECLIPSE-408 at 1/12/09 5:11 AM: - I am experiencing this too, and I think that this issue should be reopened. The .classpath file is generated incorrectly by eclipse:eclipse, regardless of the presence of the m2eclipse plugin. my settings: winXP Maven-2.0.9 maven-eclipse-plugin-2.5.14 eclipse-3.4.0 m2eclipse-plugin-0.9.6.20080905-0917 Regards, Neil Crow. See discussion on user mailing list http://www.nabble.com/Mvn-eclipse%3Aeclipse---strange-M2_REPO-settings-tt20541566.html was (Author: crowne): I am experiencing this too, and I found a jira for this issue which was closed but I think should be reopened. http://jira.codehaus.org/browse/MECLIPSE-408 my setting: winXP Maven-2.0.9 maven-eclipse-plugin-2.5.14 eclipse-3.4.0 m2eclipse-plugin-0.9.6.20080905-0917 Regards, Neil Crow. See discussion on user mailing list http://www.nabble.com/Mvn-eclipse%3Aeclipse---strange-M2_REPO-settings-tt20541566.html > eclipse:eclipse creates a .classpath containing the M2_REPO variable followed > by the expanded value of the variable > --- > > Key: MECLIPSE-408 > URL: http://jira.codehaus.org/browse/MECLIPSE-408 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Environment: MS Windows XP, + cygwin >Reporter: Gus Mancuso > Attachments: Copy of pom.xml, parentPom.xml, settings.xml > > > Using maven 2.0.8, and eclipse plugin (version 2.4 or 2.5). When I run mvn > eclipse:eclipse the .classpath that gets generated is invalid. My M2_REPO > variable is set to /var/maven and the classpath entries for dependencies look > like : >path="M2_REPO/var/maven/commons-collections/commons-collections/3.1/commons-collections-3.1.jar"/> > where >path="M2_REPO/commons-collections/commons-collections/3.1/commons-collections-3.1.jar"/> > would be the correct entry. > Things about my environment that may be affecting this: > * I run maven from a cygwin bash prompt. > * /var/maven is a symlink to /cygdrive/c/var/maven > * MAVEN_HOME is C:\opt\maven-2.0.8 > settings.xml and pom.xml for the affected project is included. It should be > noted that some other projects on the same machine seem to work fine, but > others dont. I don't see any -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-274) Broken link in "What is Doxia?" page
Broken link in "What is Doxia?" page Key: DOXIA-274 URL: http://jira.codehaus.org/browse/DOXIA-274 Project: Maven Doxia Issue Type: Bug Components: Documentation Reporter: Trevor Harmon Priority: Minor The following page has a broken link: http://maven.apache.org/doxia/ The link to "Aptconvert" is broken. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-275) Block level elements are ignored in HTML output
Block level elements are ignored in HTML output --- Key: DOXIA-275 URL: http://jira.codehaus.org/browse/DOXIA-275 Project: Maven Doxia Issue Type: Bug Components: Module - Apt Reporter: Trevor Harmon The APT format includes a facility for specifying the title, author, and date of the document, as described here: http://maven.apache.org/doxia/references/apt-format.html For example: -- Title -- Author -- Date However, after running "mvn site", these elements do not appear in the text of the generated HTML. The title is only placed in the HTML's element, not anywhere in the body. The author is in a tag, which cannot be seen without looking at the source. And the date doesn't seem to be put anywhere at all. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEAR-70) loader-repository node for jboss configuration
[
http://jira.codehaus.org/browse/MEAR-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160733#action_160733
]
Kyle S. Bober commented on MEAR-70:
---
Just curious if any progress has been made on this issue. I am attempting to
set the loader-repository-config for one of my jboss-app.xml file via Maven2
EAR plugin and it doesn't seem to support this element. Is there a current work
around?
> loader-repository node for jboss configuration
> --
>
> Key: MEAR-70
> URL: http://jira.codehaus.org/browse/MEAR-70
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Mark Kettner
> Fix For: 2.4
>
>
> I added the patch MEAR-50.patch to the 2.3 version of the maven-ear-plugin.
> However, after the patch I still couldn't generate a correct jboss-app.xml
> file when the pom.xml contained the following definition:
>
>
>
> org.apache.maven.plugins
> maven-ear-plugin
> 2.3.1
>
>
> 4
>
>nl.ictu.spg.bsn:loader=afslagbsn
>
> java2ParentDelegation=false
>
>
>
>
>
>
> This is because in the file AbstractEarMojo the
> final String loaderRepository = jboss.getChild(
> JbossConfiguration.LOADER_REPOSITORY ).getValue();
> is null when a subtag is added to the loaderRepository tag.
> This can be solved by changing the definition in the pom.xml file to the
> following:
>
>
>
> org.apache.maven.plugins
> maven-ear-plugin
> 2.3.1
>
>
> 4
>
>
>
>
>
>
>
> and change the "write" method in the JbossAppXmlWriter class to the following:
> // classloader repository
> if ( jbossConfiguration.getLoaderRepository() != null )
> {
> writer.startElement( JbossConfiguration.LOADER_REPOSITORY );
> writer.writeMarkup( jbossConfiguration.getLoaderRepository() );
> writer.endElement();
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEAR-70) loader-repository node for jboss configuration
[
http://jira.codehaus.org/browse/MEAR-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160735#action_160735
]
Stephane Nicoll commented on MEAR-70:
-
Nope but given the number of votes, that's probably the next one we'll
implement.
> loader-repository node for jboss configuration
> --
>
> Key: MEAR-70
> URL: http://jira.codehaus.org/browse/MEAR-70
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Mark Kettner
> Fix For: 2.4
>
>
> I added the patch MEAR-50.patch to the 2.3 version of the maven-ear-plugin.
> However, after the patch I still couldn't generate a correct jboss-app.xml
> file when the pom.xml contained the following definition:
>
>
>
> org.apache.maven.plugins
> maven-ear-plugin
> 2.3.1
>
>
> 4
>
>nl.ictu.spg.bsn:loader=afslagbsn
>
> java2ParentDelegation=false
>
>
>
>
>
>
> This is because in the file AbstractEarMojo the
> final String loaderRepository = jboss.getChild(
> JbossConfiguration.LOADER_REPOSITORY ).getValue();
> is null when a subtag is added to the loaderRepository tag.
> This can be solved by changing the definition in the pom.xml file to the
> following:
>
>
>
> org.apache.maven.plugins
> maven-ear-plugin
> 2.3.1
>
>
> 4
>
>
>
>
>
>
>
> and change the "write" method in the JbossAppXmlWriter class to the following:
> // classloader repository
> if ( jbossConfiguration.getLoaderRepository() != null )
> {
> writer.startElement( JbossConfiguration.LOADER_REPOSITORY );
> writer.writeMarkup( jbossConfiguration.getLoaderRepository() );
> writer.endElement();
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEAR-70) loader-repository node for jboss configuration
[
http://jira.codehaus.org/browse/MEAR-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160736#action_160736
]
Benjamin commented on MEAR-70:
--
here is an ugly workaround:
manually create your jboss-app.xml file (with the loader-repository-config
element) in a directory named src/main/application. if your ear has
dependencies on jboss-specific types like sars/hars, then you will need to
manually define these in the jboss-app.xml file as well.
in your ear's pom.xml configure the ear plugin as follows:
org.apache.maven.plugins
maven-ear-plugin
4
when you go to build the ear, it will generate a jboss-app.xml file, then it
will copy your jboss-app.xml file from the src/main/application directory and
overwrite the one it created, then it will bundle all the stuff into the ear.
it is important to add the jboss configuration element because if you don't,
then the ear module will attempt to add jboss-specific types (like sars/hars)
to your application.xml file. If your ear module only has dependencies on the
three normal types (ejb/rar/war), then you dont need the jboss config element
in your pom at all.
its ugly since you need to hardcode your own jboss-app.xml file but it seemed
to work for me. i dont understand why the ability to configure the
loader-repository-config element wasn't added from the start considering it is
so trivial.
> loader-repository node for jboss configuration
> --
>
> Key: MEAR-70
> URL: http://jira.codehaus.org/browse/MEAR-70
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Mark Kettner
> Fix For: 2.4
>
>
> I added the patch MEAR-50.patch to the 2.3 version of the maven-ear-plugin.
> However, after the patch I still couldn't generate a correct jboss-app.xml
> file when the pom.xml contained the following definition:
>
>
>
> org.apache.maven.plugins
> maven-ear-plugin
> 2.3.1
>
>
> 4
>
>nl.ictu.spg.bsn:loader=afslagbsn
>
> java2ParentDelegation=false
>
>
>
>
>
>
> This is because in the file AbstractEarMojo the
> final String loaderRepository = jboss.getChild(
> JbossConfiguration.LOADER_REPOSITORY ).getValue();
> is null when a subtag is added to the loaderRepository tag.
> This can be solved by changing the definition in the pom.xml file to the
> following:
>
>
>
> org.apache.maven.plugins
> maven-ear-plugin
> 2.3.1
>
>
> 4
>
>
>
>
>
>
>
> and change the "write" method in the JbossAppXmlWriter class to the following:
> // classloader repository
> if ( jbossConfiguration.getLoaderRepository() != null )
> {
> writer.startElement( JbossConfiguration.LOADER_REPOSITORY );
> writer.writeMarkup( jbossConfiguration.getLoaderRepository() );
> writer.endElement();
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-276) Typo in "Proposed Changes to the APT Format"
Typo in "Proposed Changes to the APT Format" Key: DOXIA-276 URL: http://jira.codehaus.org/browse/DOXIA-276 Project: Maven Doxia Issue Type: Bug Components: Documentation Reporter: Trevor Harmon Priority: Trivial http://docs.codehaus.org/display/DOXIA/Proposed+Changes+to+the+APT+Format "it's limitations" should be "its limitations" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2326) Please add
Please add --- Key: MAVENUPLOAD-2326 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2326 Project: Maven Upload Requests Issue Type: Wish Reporter: Ivan Szkiba "net.sourceforge.tink","mavens...@web.sourceforge.net:/home/groups/t/ti/tink/repository/release","rsync_ssh","Ivan Szkiba","szk...@users.sourceforge.net",, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVEN-1542) Merge build elements in extended POM
[
http://jira.codehaus.org/browse/MAVEN-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160744#action_160744
]
Stefan Franke commented on MAVEN-1542:
--
Would be easy to fix, if you add an to the resources.
This way you could
- merge, if IDs are different
- override, if IDs match
- remove, if IDs match and rest of overriding element is empty
> Merge build elements in extended POM
>
>
> Key: MAVEN-1542
> URL: http://jira.codehaus.org/browse/MAVEN-1542
> Project: Maven 1
> Issue Type: Improvement
> Components: inheritance
>Affects Versions: 1.0.2
>Reporter: Steven Caswell
>Priority: Minor
>
> Resources and unit test include/exclude patterns in the build element are not
> inherited, which presents issues for subprojects that need to add to the
> existing parent project. Please change maven to allow these elements to be
> merged rather than replaced.
> For example, a parent project.xml might include the following:
>
>
>
>
> src/test/resources
> resources
>
>**/*.*
>
>
>
> ${basedir}/../resources
>
>log4j-sample.properties
>beanRefFactory.xml
>aspectwerkz.xml
>
>
>
> ${basedir}/../resources/context
> context
>
>**/*.*
>
>
>
>
>
> A subproject's project.xml might need to add an additional resources:
>
>
>
>
> ../interface/target/test-classes
>
>
>**/*.class
>
>
>
>
>
> 1.0.2 replaces the parent project's unitTest resources with that defined in
> the subproject. This improvement requests that they be merged, so the
> equivalent would be as follows:
>
>
>
>
>
> src/test/resources
> resources
>
>**/*.*
>
>
>
> ${basedir}/../resources
>
>log4j-sample.properties
>beanRefFactory.xml
>aspectwerkz.xml
>
>
>
> ${basedir}/../resources/context
> context
>
>**/*.*
>
>
>
>
> ../interface/target/test-classes
>
>
>**/*.class
>
>
>
>
>
> A bit of preliminary discussion from the user's mailing list:
> http://marc.theaimsgroup.com/?l=turbine-maven-user&m=110423829501521&w=2
> http://marc.theaimsgroup.com/?l=turbine-maven-dev&m=110428720508765&w=2
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MECLIPSE-408) eclipse:eclipse creates a .classpath containing the M2_REPO variable followed by the expanded value of the variable
[ http://jira.codehaus.org/browse/MECLIPSE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrie Treloar reopened MECLIPSE-408: - Assignee: Barrie Treloar > eclipse:eclipse creates a .classpath containing the M2_REPO variable followed > by the expanded value of the variable > --- > > Key: MECLIPSE-408 > URL: http://jira.codehaus.org/browse/MECLIPSE-408 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Environment: MS Windows XP, + cygwin >Reporter: Gus Mancuso >Assignee: Barrie Treloar > Attachments: Copy of pom.xml, parentPom.xml, settings.xml > > > Using maven 2.0.8, and eclipse plugin (version 2.4 or 2.5). When I run mvn > eclipse:eclipse the .classpath that gets generated is invalid. My M2_REPO > variable is set to /var/maven and the classpath entries for dependencies look > like : >path="M2_REPO/var/maven/commons-collections/commons-collections/3.1/commons-collections-3.1.jar"/> > where >path="M2_REPO/commons-collections/commons-collections/3.1/commons-collections-3.1.jar"/> > would be the correct entry. > Things about my environment that may be affecting this: > * I run maven from a cygwin bash prompt. > * /var/maven is a symlink to /cygdrive/c/var/maven > * MAVEN_HOME is C:\opt\maven-2.0.8 > settings.xml and pom.xml for the affected project is included. It should be > noted that some other projects on the same machine seem to work fine, but > others dont. I don't see any -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEAR-70) loader-repository node for jboss configuration
[
http://jira.codehaus.org/browse/MEAR-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160748#action_160748
]
Stephane Nicoll commented on MEAR-70:
-
Can you describe how you find this trivial? What would be your solution?
> loader-repository node for jboss configuration
> --
>
> Key: MEAR-70
> URL: http://jira.codehaus.org/browse/MEAR-70
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Mark Kettner
> Fix For: 2.4
>
>
> I added the patch MEAR-50.patch to the 2.3 version of the maven-ear-plugin.
> However, after the patch I still couldn't generate a correct jboss-app.xml
> file when the pom.xml contained the following definition:
>
>
>
> org.apache.maven.plugins
> maven-ear-plugin
> 2.3.1
>
>
> 4
>
>nl.ictu.spg.bsn:loader=afslagbsn
>
> java2ParentDelegation=false
>
>
>
>
>
>
> This is because in the file AbstractEarMojo the
> final String loaderRepository = jboss.getChild(
> JbossConfiguration.LOADER_REPOSITORY ).getValue();
> is null when a subtag is added to the loaderRepository tag.
> This can be solved by changing the definition in the pom.xml file to the
> following:
>
>
>
> org.apache.maven.plugins
> maven-ear-plugin
> 2.3.1
>
>
> 4
>
>
>
>
>
>
>
> and change the "write" method in the JbossAppXmlWriter class to the following:
> // classloader repository
> if ( jbossConfiguration.getLoaderRepository() != null )
> {
> writer.startElement( JbossConfiguration.LOADER_REPOSITORY );
> writer.writeMarkup( jbossConfiguration.getLoaderRepository() );
> writer.endElement();
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3966) Requirements (User Story)
[ http://jira.codehaus.org/browse/MNG-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov closed MNG-3966. - Resolution: Fixed done > Requirements (User Story) > - > > Key: MNG-3966 > URL: http://jira.codehaus.org/browse/MNG-3966 > Project: Maven 2 > Issue Type: Sub-task > Components: Artifacts and Repositories >Affects Versions: 3.0-alpha-1 >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 3.0-alpha-2 > > > *Delta Manager* story: > * standalone library > * CLI wrapper > * is run for a particular maven instance on disk > ** lists all the available "compatible" versions (like 3.0.* family) > ** allows to up / down grade current instance to any of available > "compatible" version > ** works on binaries only ( the ./lib folder), all other files presumed > installed and compatible > *Installer* story: > * standalone library > * CLI wrapper > * maintains a set of "maven distributions" on user disk > * allows user to > ** list local "installed" distributions (inventory function) > ** list available remote distributions > ** install a version > ** remove a version > ** switch > First deliverable shall provide *Delta Manager* implementation -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3967) Design
[ http://jira.codehaus.org/browse/MNG-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov closed MNG-3967. - Resolution: Fixed done > Design > -- > > Key: MNG-3967 > URL: http://jira.codehaus.org/browse/MNG-3967 > Project: Maven 2 > Issue Type: Sub-task > Components: Artifacts and Repositories >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 3.0-alpha-2 > > > First deliverable shall > * be designed as part of a more complex provisioning system > ** provide APIs to be later used by that system > * implement *Delta Management* requirements from [MNG-3966] > When started with a pointer to a maven instance, it shall: > * find *maven-distribution-xx.jar* in ./lib to use for *current version* > * retrieve all existing versions of the "same family" (a'la 3.0.xx) for > *org.apache.maven:maven-distribution:3.0.xx* > * let user supply a version to up / down grade to > * calculate, using Mercury APIs > ** runtime scoped classpath for "current" pom.xml > ** runtime scoped classpath for selected version's pom.xml > ** retrieve the binary diff to local repo > * make ./lib reflect the "new" runtime classpath > ** remove replaced binaries > ** copy in missing binaries -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3981) implement update GUI
implement update GUI Key: MNG-3981 URL: http://jira.codehaus.org/browse/MNG-3981 Project: Maven 2 Issue Type: Sub-task Reporter: Oleg Gusakov -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3980) implement delta management CLI
implement delta management CLI -- Key: MNG-3980 URL: http://jira.codehaus.org/browse/MNG-3980 Project: Maven 2 Issue Type: Sub-task Reporter: Oleg Gusakov Assignee: Oleg Gusakov -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3968) Deployment Descriptor
[ http://jira.codehaus.org/browse/MNG-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov closed MNG-3968. - Resolution: Fixed done > Deployment Descriptor > - > > Key: MNG-3968 > URL: http://jira.codehaus.org/browse/MNG-3968 > Project: Maven 2 > Issue Type: Sub-task > Components: Artifacts and Repositories >Affects Versions: 3.0-alpha-1 >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 3.0-alpha-2 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (MNG-3980) implement delta management CLI
[ http://jira.codehaus.org/browse/MNG-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-3980 started by Oleg Gusakov. > implement delta management CLI > -- > > Key: MNG-3980 > URL: http://jira.codehaus.org/browse/MNG-3980 > Project: Maven 2 > Issue Type: Sub-task >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3980) implement delta management CLI
[ http://jira.codehaus.org/browse/MNG-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MNG-3980: -- Description: allow dependencies like LATEST or SNAPSHOT be processed correctly in the configuration descriptor Affects Version/s: 3.0-alpha-1 Fix Version/s: 3.0-alpha-2 Component/s: Bootstrap & Build > implement delta management CLI > -- > > Key: MNG-3980 > URL: http://jira.codehaus.org/browse/MNG-3980 > Project: Maven 2 > Issue Type: Sub-task > Components: Bootstrap & Build >Affects Versions: 3.0-alpha-1 >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 3.0-alpha-2 > > > allow dependencies like LATEST or SNAPSHOT be processed correctly in the > configuration descriptor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3981) implement update GUI
[ http://jira.codehaus.org/browse/MNG-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MNG-3981: -- Affects Version/s: 3.0-alpha-1 Fix Version/s: 3.0-alpha-2 Component/s: Dependencies > implement update GUI > > > Key: MNG-3981 > URL: http://jira.codehaus.org/browse/MNG-3981 > Project: Maven 2 > Issue Type: Sub-task > Components: Dependencies >Affects Versions: 3.0-alpha-1 >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 3.0-alpha-2 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3980) implement delta management CLI
[ http://jira.codehaus.org/browse/MNG-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov closed MNG-3980. - Resolution: Fixed implemented, virtual versions (LATEST, SNAPSHOT, ranges) addressed > implement delta management CLI > -- > > Key: MNG-3980 > URL: http://jira.codehaus.org/browse/MNG-3980 > Project: Maven 2 > Issue Type: Sub-task > Components: Bootstrap & Build >Affects Versions: 3.0-alpha-1 >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 3.0-alpha-2 > > > allow dependencies like LATEST or SNAPSHOT be processed correctly in the > configuration descriptor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3982) setup grid build
setup grid build Key: MNG-3982 URL: http://jira.codehaus.org/browse/MNG-3982 Project: Maven 2 Issue Type: Sub-task Reporter: Oleg Gusakov Assignee: Oleg Gusakov -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (MNG-3982) setup grid build
[ http://jira.codehaus.org/browse/MNG-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-3982 started by Oleg Gusakov. > setup grid build > > > Key: MNG-3982 > URL: http://jira.codehaus.org/browse/MNG-3982 > Project: Maven 2 > Issue Type: Sub-task >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3983) Plugin Repositories Not Injected From Profile
Plugin Repositories Not Injected From Profile - Key: MNG-3983 URL: http://jira.codehaus.org/browse/MNG-3983 Project: Maven 2 Issue Type: Bug Components: Profiles Affects Versions: 3.0-alpha-1 Reporter: Shane Isbell Fix For: 3.0-alpha-2 Plugin repositories are not being injected from an active profile. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3983) Plugin Repositories Not Injected From Profile
[ http://jira.codehaus.org/browse/MNG-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160762#action_160762 ] Shane Isbell commented on MNG-3983: --- Fix in, just need to add test. > Plugin Repositories Not Injected From Profile > - > > Key: MNG-3983 > URL: http://jira.codehaus.org/browse/MNG-3983 > Project: Maven 2 > Issue Type: Bug > Components: Profiles >Affects Versions: 3.0-alpha-1 >Reporter: Shane Isbell >Assignee: Shane Isbell > Fix For: 3.0-alpha-2 > > > Plugin repositories are not being injected from an active profile. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3983) Plugin Repositories Not Injected From Profile
[ http://jira.codehaus.org/browse/MNG-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3983: -- Fix Version/s: 3.0-alpha-2 > Plugin Repositories Not Injected From Profile > - > > Key: MNG-3983 > URL: http://jira.codehaus.org/browse/MNG-3983 > Project: Maven 2 > Issue Type: Bug > Components: Profiles >Affects Versions: 3.0-alpha-1 >Reporter: Shane Isbell >Assignee: Shane Isbell > Fix For: 3.0-alpha-2 > > > Plugin repositories are not being injected from an active profile. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MERCURY-38) decouple event framework into a standalone library
[ http://jira.codehaus.org/browse/MERCURY-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov closed MERCURY-38. --- Resolution: Fixed done > decouple event framework into a standalone library > -- > > Key: MERCURY-38 > URL: http://jira.codehaus.org/browse/MERCURY-38 > Project: Mercury > Issue Type: Task > Components: Misc/All >Affects Versions: 1.0.0-alpha-1 >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 1.0.0-alpha-3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MERCURY-23) replace components in maven-3.0-alpha-2 with Mercury
[ http://jira.codehaus.org/browse/MERCURY-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MERCURY-23: Fix Version/s: (was: 1.0.0-alpha-3) 1.0.0-alpha-4 > replace components in maven-3.0-alpha-2 with Mercury > > > Key: MERCURY-23 > URL: http://jira.codehaus.org/browse/MERCURY-23 > Project: Mercury > Issue Type: Task > Components: Misc/All >Affects Versions: 1.0.0-alpha-1 >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 1.0.0-alpha-4 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3984) Different types of ID Model containers joined if their ids match
[ http://jira.codehaus.org/browse/MNG-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3984: -- Fix Version/s: 3.0-alpha-2 Fix is in, still need test. > Different types of ID Model containers joined if their ids match > > > Key: MNG-3984 > URL: http://jira.codehaus.org/browse/MNG-3984 > Project: Maven 2 > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 3.0-alpha-2 >Reporter: Shane Isbell >Assignee: Shane Isbell > Fix For: 3.0-alpha-2 > > > Different types of ID Model containers are being joined if their ids matched > (plugin repository and repository). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3984) Different types of ID Model containers joined if their ids match
Different types of ID Model containers joined if their ids match Key: MNG-3984 URL: http://jira.codehaus.org/browse/MNG-3984 Project: Maven 2 Issue Type: Bug Components: Inheritance and Interpolation Affects Versions: 3.0-alpha-2 Reporter: Shane Isbell Fix For: 3.0-alpha-2 Different types of ID Model containers are being joined if their ids matched (plugin repository and repository). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3985) Missing repository and plugin repositories
Missing repository and plugin repositories -- Key: MNG-3985 URL: http://jira.codehaus.org/browse/MNG-3985 Project: Maven 2 Issue Type: Bug Components: Inheritance and Interpolation Affects Versions: 3.0-alpha-2 Reporter: Shane Isbell Fix For: 3.0-alpha-2 One one repository and/or plugin repository is showing up, when there should be multiple. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MERCURY-54) make absense of metadata in the repository clearer to the client.
[ http://jira.codehaus.org/browse/MERCURY-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MERCURY-54: Fix Version/s: 1.0.0-alpha-3 > make absense of metadata in the repository clearer to the client. > -- > > Key: MERCURY-54 > URL: http://jira.codehaus.org/browse/MERCURY-54 > Project: Mercury > Issue Type: Improvement > Components: Repository >Affects Versions: 1.0.0-alpha-3 >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 1.0.0-alpha-3 > > > For some reason - only a null exception is thrown. > Find a way to convey this information to the client code. > One way would be an event ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3985) Missing repository and plugin repositories
[ http://jira.codehaus.org/browse/MNG-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3985: -- Affects Version/s: (was: 3.0-alpha-2) 3.0-alpha-1 Fix Version/s: 3.0-alpha-2 Fix is in, still need test. > Missing repository and plugin repositories > -- > > Key: MNG-3985 > URL: http://jira.codehaus.org/browse/MNG-3985 > Project: Maven 2 > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 3.0-alpha-1 >Reporter: Shane Isbell >Assignee: Shane Isbell > Fix For: 3.0-alpha-2 > > > One one repository and/or plugin repository is showing up, when there should > be multiple. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MERCURY-54) make absense of metadata in the repository clearer to the client.
[ http://jira.codehaus.org/browse/MERCURY-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160765#action_160765 ] Oleg Gusakov commented on MERCURY-54: - fixed in the trunk > make absense of metadata in the repository clearer to the client. > -- > > Key: MERCURY-54 > URL: http://jira.codehaus.org/browse/MERCURY-54 > Project: Mercury > Issue Type: Improvement > Components: Repository >Affects Versions: 1.0.0-alpha-3 >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 1.0.0-alpha-3 > > > For some reason - only a null exception is thrown. > Find a way to convey this information to the client code. > One way would be an event ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3986) Remote repos not being used if it is in a profile
[ http://jira.codehaus.org/browse/MNG-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3986: -- Fix Version/s: 3.0-alpha-2 Fixed, still need test. > Remote repos not being used if it is in a profile > - > > Key: MNG-3986 > URL: http://jira.codehaus.org/browse/MNG-3986 > Project: Maven 2 > Issue Type: Bug > Components: Profiles >Affects Versions: 3.0-alpha-1 >Reporter: Shane Isbell >Assignee: Shane Isbell > Fix For: 3.0-alpha-2 > > > Remote repos not being used if it is in an active profile. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3986) Remote repos not being used if it is in a profile
Remote repos not being used if it is in a profile - Key: MNG-3986 URL: http://jira.codehaus.org/browse/MNG-3986 Project: Maven 2 Issue Type: Bug Components: Profiles Affects Versions: 3.0-alpha-1 Reporter: Shane Isbell Fix For: 3.0-alpha-2 Remote repos not being used if it is in an active profile. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MERCURY-54) make absense of metadata in the repository clearer to the client.
[ http://jira.codehaus.org/browse/MERCURY-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160765#action_160765 ] Oleg Gusakov edited comment on MERCURY-54 at 1/12/09 8:49 PM: -- fixed in the trunk need more ITs to test edge cases was (Author: olle): fixed in the trunk > make absense of metadata in the repository clearer to the client. > -- > > Key: MERCURY-54 > URL: http://jira.codehaus.org/browse/MERCURY-54 > Project: Mercury > Issue Type: Improvement > Components: Repository >Affects Versions: 1.0.0-alpha-3 >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 1.0.0-alpha-3 > > > For some reason - only a null exception is thrown. > Find a way to convey this information to the client code. > One way would be an event ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (MNG-3984) Different types of ID Model containers joined if their ids match
[ http://jira.codehaus.org/browse/MNG-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-3984 started by Shane Isbell. > Different types of ID Model containers joined if their ids match > > > Key: MNG-3984 > URL: http://jira.codehaus.org/browse/MNG-3984 > Project: Maven 2 > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 3.0-alpha-2 >Reporter: Shane Isbell >Assignee: Shane Isbell > Fix For: 3.0-alpha-2 > > > Different types of ID Model containers are being joined if their ids matched > (plugin repository and repository). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (MNG-3986) Remote repos not being used if it is in a profile
[ http://jira.codehaus.org/browse/MNG-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-3986 started by Shane Isbell. > Remote repos not being used if it is in a profile > - > > Key: MNG-3986 > URL: http://jira.codehaus.org/browse/MNG-3986 > Project: Maven 2 > Issue Type: Bug > Components: Profiles >Affects Versions: 3.0-alpha-1 >Reporter: Shane Isbell >Assignee: Shane Isbell > Fix For: 3.0-alpha-2 > > > Remote repos not being used if it is in an active profile. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (MNG-3985) Missing repository and plugin repositories
[ http://jira.codehaus.org/browse/MNG-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-3985 started by Shane Isbell. > Missing repository and plugin repositories > -- > > Key: MNG-3985 > URL: http://jira.codehaus.org/browse/MNG-3985 > Project: Maven 2 > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 3.0-alpha-1 >Reporter: Shane Isbell >Assignee: Shane Isbell > Fix For: 3.0-alpha-2 > > > One one repository and/or plugin repository is showing up, when there should > be multiple. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MERCURY-59) Add svn props for source files
[ http://jira.codehaus.org/browse/MERCURY-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MERCURY-59: Fix Version/s: 1.0.0-alpha-3 > Add svn props for source files > -- > > Key: MERCURY-59 > URL: http://jira.codehaus.org/browse/MERCURY-59 > Project: Mercury > Issue Type: Task > Components: Misc/All >Reporter: Benjamin Bentmann >Assignee: Oleg Gusakov >Priority: Minor > Fix For: 1.0.0-alpha-3 > > > Several newer source files are lacking svn props as outlined in [Maven > Committer > Environment|http://maven.apache.org/developers/committer-environment.html], > especially svn:eol-style=native is crucial for proper inter-op between > Windows and Unix. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MERCURY-59) Add svn props for source files
[ http://jira.codehaus.org/browse/MERCURY-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov closed MERCURY-59. --- Resolution: Fixed done > Add svn props for source files > -- > > Key: MERCURY-59 > URL: http://jira.codehaus.org/browse/MERCURY-59 > Project: Mercury > Issue Type: Task > Components: Misc/All >Reporter: Benjamin Bentmann >Assignee: Oleg Gusakov >Priority: Minor > Fix For: 1.0.0-alpha-3 > > > Several newer source files are lacking svn props as outlined in [Maven > Committer > Environment|http://maven.apache.org/developers/committer-environment.html], > especially svn:eol-style=native is crucial for proper inter-op between > Windows and Unix. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3987) No attempts to connect to remote repositories under Sun JDK 1.6.0.06 (i386 and x86_64)
No attempts to connect to remote repositories under Sun JDK 1.6.0.06 (i386 and x86_64) --- Key: MNG-3987 URL: http://jira.codehaus.org/browse/MNG-3987 Project: Maven 2 Issue Type: Bug Components: Dependencies Environment: Fedora 10 (2.6.27.5-117.fc10.x86_64) Sun jdk1.6.0_06-x86_64 Maven 2.0.9 Reporter: Andrew Lee Rubinger While using Sun jdk1.6.0_06-x86_64 as JAVA_HOME, remote dependencies are not downloaded. Wireshark network analysis shows no TCP requests sent out of port 80. Using jdk1.6.0_11-x86_64 resolves the issue. Steps to duplicate (on the reporter's local environment) 1) Clean local M2 repo (ie. ~/.m2/repository) 2) Set JAVA_HOME to jdk1.6.0_06-x86_64 3) Attempt "mvn install"..Observe dependency resolution problems as artifacts and POMs cannot be downloaded. Maven reports as not found. The URLs noted in the trace are accessible via wget or browser. 4) Set JAVA_HOME to jdk1.6.0_11-x86_64 5) Attempt "mvn install" Dependencies will be downloaded. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3987) No attempts to connect to remote repositories under Sun JDK 1.6.0.06 (i386 and x86_64)
[ http://jira.codehaus.org/browse/MNG-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lee Rubinger updated MNG-3987: - Attachment: maven_dependency_resolution_fail-jdk1.6.0_06-x86_64.txt Attached "mvn install -X" resolution failing under jdk1.6.0_06-x86_64 > No attempts to connect to remote repositories under Sun JDK 1.6.0.06 (i386 > and x86_64) > --- > > Key: MNG-3987 > URL: http://jira.codehaus.org/browse/MNG-3987 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies > Environment: Fedora 10 (2.6.27.5-117.fc10.x86_64) > Sun jdk1.6.0_06-x86_64 > Maven 2.0.9 >Reporter: Andrew Lee Rubinger > Attachments: maven_dependency_resolution_fail-jdk1.6.0_06-x86_64.txt > > > While using Sun jdk1.6.0_06-x86_64 as JAVA_HOME, remote dependencies are not > downloaded. Wireshark network analysis shows no TCP requests sent out of > port 80. Using jdk1.6.0_11-x86_64 resolves the issue. > Steps to duplicate (on the reporter's local environment) > 1) Clean local M2 repo (ie. ~/.m2/repository) > 2) Set JAVA_HOME to jdk1.6.0_06-x86_64 > 3) Attempt "mvn install"..Observe dependency resolution problems as artifacts > and POMs cannot be downloaded. Maven reports as not found. The URLs noted > in the trace are accessible via wget or browser. > 4) Set JAVA_HOME to jdk1.6.0_11-x86_64 > 5) Attempt "mvn install" Dependencies will be downloaded. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3987) No attempts to connect to remote repositories under Sun JDK 1.6.0.06 (i386 and x86_64)
[ http://jira.codehaus.org/browse/MNG-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lee Rubinger updated MNG-3987: - Attachment: maven_dependency_resolution_works-jdk1.6.0_11-x86_64.txt Attached output of "mvn install -X" using jdk1.6.0_11-x86_64 > No attempts to connect to remote repositories under Sun JDK 1.6.0.06 (i386 > and x86_64) > --- > > Key: MNG-3987 > URL: http://jira.codehaus.org/browse/MNG-3987 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies > Environment: Fedora 10 (2.6.27.5-117.fc10.x86_64) > Sun jdk1.6.0_06-x86_64 > Maven 2.0.9 >Reporter: Andrew Lee Rubinger > Attachments: maven_dependency_resolution_fail-jdk1.6.0_06-x86_64.txt, > maven_dependency_resolution_works-jdk1.6.0_11-x86_64.txt > > > While using Sun jdk1.6.0_06-x86_64 as JAVA_HOME, remote dependencies are not > downloaded. Wireshark network analysis shows no TCP requests sent out of > port 80. Using jdk1.6.0_11-x86_64 resolves the issue. > Steps to duplicate (on the reporter's local environment) > 1) Clean local M2 repo (ie. ~/.m2/repository) > 2) Set JAVA_HOME to jdk1.6.0_06-x86_64 > 3) Attempt "mvn install"..Observe dependency resolution problems as artifacts > and POMs cannot be downloaded. Maven reports as not found. The URLs noted > in the trace are accessible via wget or browser. > 4) Set JAVA_HOME to jdk1.6.0_11-x86_64 > 5) Attempt "mvn install" Dependencies will be downloaded. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (MNG-3981) implement update GUI
[ http://jira.codehaus.org/browse/MNG-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-3981 started by Oleg Gusakov. > implement update GUI > > > Key: MNG-3981 > URL: http://jira.codehaus.org/browse/MNG-3981 > Project: Maven 2 > Issue Type: Sub-task > Components: Dependencies >Affects Versions: 3.0-alpha-1 >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 3.0-alpha-2 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3982) setup grid build
[ http://jira.codehaus.org/browse/MNG-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MNG-3982: -- Remaining Estimate: (was: 1 hour) Original Estimate: (was: 1 hour) > setup grid build > > > Key: MNG-3982 > URL: http://jira.codehaus.org/browse/MNG-3982 > Project: Maven 2 > Issue Type: Sub-task >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
