[jira] Commented: (MECLIPSE-132) "Class not found" when run/debug JUnit tests
[ http://jira.codehaus.org/browse/MECLIPSE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152395#action_152395 ] Cameron Rich commented on MECLIPSE-132: --- See http://blog.xemantic.com/2008/06/maven-integration-for-eclipse-and.html?widgetType=BlogArchive&widgetId=BlogArchive1&action=toggle&dir=close&toggle=YEARLY-119914200&toggleopen=MONTHLY-122022000 > "Class not found" when run/debug JUnit tests > > > Key: MECLIPSE-132 > URL: http://jira.codehaus.org/browse/MECLIPSE-132 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path > (.classpath), M2Eclipse support > Environment: gentoo linux 2006, kernel 2.6, sun-jdk-1.5.0.06, maven > 2.0.4, eclipse sdk 3.2, myeclipse 5 m2 >Reporter: Diego Ballve > Attachments: maven-sample.zip > > > This is for the behavior described in > http://www.nabble.com/Keep-getting-%22Class-not-found%22-when-running-debugging-JUnit-tests-tf1851758.html#a5442440 > You get "Class not found" when running/debuging JUnit tests. > For me it happened when I was importing another project and its dependencies > (both m2 projects). > Clean compile works fine, problem is with run. > The workaround to get it working is: > In the project containing your tests, edit Java Build Path | Order and > Export: Make sure M2 Dependencies appears BEFORE JRE System Library. > Thanks, > Diego -- 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: (ARCHETYPE-219) Warning messages for properties in pom.xml files
[
http://jira.codehaus.org/browse/ARCHETYPE-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152381#action_152381
]
Pat Podenski commented on ARCHETYPE-219:
In the description above I failed to mention that for files other than the
pom.xml files, the archetype already does the escaping as described above -- it
just doesn't do the escape markup for pom.xml files.
> Warning messages for properties in pom.xml files
>
>
> Key: ARCHETYPE-219
> URL: http://jira.codehaus.org/browse/ARCHETYPE-219
> Project: Maven Archetype
> Issue Type: Bug
>Affects Versions: 2.0-alpha-4
> Environment: Windows or Mac OS X
> Apache Maven 2.0.9
>Reporter: Pat Podenski
>Priority: Minor
> Attachments: foo-archetype.zip
>
>
> Property expression in pom.xml are not escaped when creating an archetype
> from a project. As a result warning messages appear during project creation
> from the archetype.
> I was able to eliminate the warning messages by escaping the property
> expressions. For example, in a pom.xml file, I added a #set for escaping '$'
> at the beginning of the pom.xml and then applied the escape to the property
> expression as shown below:
> #set( $symbol_dollar = '$' )
>
>
>
> ${symbol_dollar}{basedir}/src/main/resources
> If the archetype plugin would detect these property expressions and provide
> the escaping, then it would not be necessary to go through each pom.xml
> (e.g., in a multimodule project) and hand edit the escapes for property
> expressions.
> I am enclosing a simple multimodule project archetype in which I added the
> escape by hand editing the pom.xml of the sub module.
--
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: (ARCHETYPE-219) Warning messages for properties in pom.xml files
Warning messages for properties in pom.xml files
Key: ARCHETYPE-219
URL: http://jira.codehaus.org/browse/ARCHETYPE-219
Project: Maven Archetype
Issue Type: Bug
Affects Versions: 2.0-alpha-4
Environment: Windows or Mac OS X
Apache Maven 2.0.9
Reporter: Pat Podenski
Priority: Minor
Attachments: foo-archetype.zip
Property expression in pom.xml are not escaped when creating an archetype from
a project. As a result warning messages appear during project creation from the
archetype.
I was able to eliminate the warning messages by escaping the property
expressions. For example, in a pom.xml file, I added a #set for escaping '$' at
the beginning of the pom.xml and then applied the escape to the property
expression as shown below:
#set( $symbol_dollar = '$' )
${symbol_dollar}{basedir}/src/main/resources
If the archetype plugin would detect these property expressions and provide the
escaping, then it would not be necessary to go through each pom.xml (e.g., in a
multimodule project) and hand edit the escapes for property expressions.
I am enclosing a simple multimodule project archetype in which I added the
escape by hand editing the pom.xml of the sub module.
--
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-3424) Respect ordering of elements as given in POM
[
http://jira.codehaus.org/browse/MNG-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MNG-3424.
-
Assignee: Brett Porter
Resolution: Fixed
Fix Version/s: (was: 2.0.11)
2.1.0-M2
2.0.10
> Respect ordering of elements as given in POM
>
>
> Key: MNG-3424
> URL: http://jira.codehaus.org/browse/MNG-3424
> Project: Maven 2
> Issue Type: Improvement
>Affects Versions: 2.0.8
>Reporter: Benjamin Bentmann
>Assignee: Brett Porter
>Priority: Trivial
> Fix For: 2.0.10, 2.1.0-M2
>
> Attachments: retain-collection-order.patch
>
>
> "Better safe than sorry" suggests to keep the ordering of collections when
> converting them into maps. It's hard to know when ordering is really
> irrelevant and the penalty of using {{java.util.Linked*}} is usually
> neglectable.
--
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: (MANTTASKS-87) Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml will cause a "Error downloading parent pom" error
[ http://jira.codehaus.org/browse/MANTTASKS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pino Silvaggio updated MANTTASKS-87: Attachment: maven-ant-tasks.jar I made my own modifications so that it works. It seems to work pretty well, I am at home right and my source is at my office, I will attach the source tomorrow. In the mean time you can use the attached fixed jar. > Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml > will cause a "Error downloading parent pom" error > - > > Key: MANTTASKS-87 > URL: http://jira.codehaus.org/browse/MANTTASKS-87 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: POM Integration >Affects Versions: 2.0.9 > Environment: WindowsXP > Ant version 1.7.0 >Reporter: Jeff Campbell >Assignee: Herve Boutemy >Priority: Blocker > Attachments: CASE.tar.gz, maven-ant-tasks.jar > > > Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml > will cause a "Error downloading parent pom" error. > This WAS NOT a bug with version 2.0.6 of the maven-ant-tasks (new issue to > maven-ant-tasks-2.0.7.jar and still an issue with the latest > maven-ant-tasks-2.0.8-SNAPSHOT.jar (as of the writting of this bug)). > Just to see if I had done something wrong with the pom.xml file I tried to > run a Maven goal against the pom.xml file. I found that if I run "mvn clean" > from this same directory (where the build.xml and pom.xml file is located), > using Maven-2.0.7, I get a build successfull (it was able to find the parent > pom.xml file... so this seems to be isolated to JUST the maven-ant-task not > being able to find the parent pom.xml) > Sample of the pom.xml file > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > intuit.sbconnect > sbclogin > 1.0.3 > SBCLogin > > > mygroup > CommonPOM > 1.0.2 > > > > > myothergroup > myartifact > 1.0 > > > > Line in Ant build.xml file that causes the error: > > Error that occurs when this line is executed in ant: > Error downloading parent pom: Missing: > -- > 1) mygroup:CommonPOM:pom:1.0.2 > Path to dependency: > 1) unspecified:unspecified:jar:0.0 > 2) mygroup:CommonPOM:pom:1.0.2 > -- > 1 required artifact is missing. > for artifact: > unspecified:unspecified:jar:0.0 > from the specified remote repositories: > central (http://repo1.maven.org/maven2) -- 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-3770) pom gets trancated when deploying to repository
[ http://jira.codehaus.org/browse/MNG-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152360#action_152360 ] elmoumen commented on MNG-3770: --- tell continuim just to deploy in maven repository, don't define twice the repository > pom gets trancated when deploying to repository > --- > > Key: MNG-3770 > URL: http://jira.codehaus.org/browse/MNG-3770 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.9 > Environment: redhat4 >Reporter: elmoumen > Attachments: good.xml, trancated.xml > > > i have a problem deploying artifacts to repository > if the artifact exists the pom is trancated else no pb > i'm using redhat4, maven2.0.9 and hudson -- 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: (MWAR-172) Allow specification of escape character to escape filter interpolation in WAR resources
[ http://jira.codehaus.org/browse/MWAR-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MWAR-172: -- Fix Version/s: 2.1 > Allow specification of escape character to escape filter interpolation in WAR > resources > --- > > Key: MWAR-172 > URL: http://jira.codehaus.org/browse/MWAR-172 > Project: Maven 2.x War Plugin > Issue Type: New Feature >Affects Versions: 2.1-alpha-2 > Environment: any >Reporter: Mike Rokitka > Fix For: 2.1 > > > The war plugin should allow users to specify an escape character to avoid > interpolation when filtering web resources. There are instances when > interpolation is not needed or results in undesired output, for example when > working with JSP 2.0 EL expressions, which may clash with filter token names. > Version 1.0-beta-2 of the maven filtering shared component includes this > functionality. > See - http://jira.codehaus.org/browse/MSHARED-51 > ~Mike -- 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-3809) Installation simply does not work - at least as described
[ http://jira.codehaus.org/browse/MNG-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Katz updated MNG-3809: -- Attachment: tobenj.txt Hi Benjamin, The network is working. I can navigate by hand to: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom And it displays the XML file. There is no proxy. I have attached the -e and a navigation (just for show) from Sam Spade to the main site and some analysis. Thanks for your help. Regard, Rich Katz (415) 336-9559 > Installation simply does not work - at least as described > - > > Key: MNG-3809 > URL: http://jira.codehaus.org/browse/MNG-3809 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: General, Errors, Plugin Requests, POM, > Settings >Affects Versions: 2.0.9 > Environment: C:\Documents and Settings\Richard Katz>mvn --version > Maven version: 2.0.9 > Java version: 1.6.0_01 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Richard Katz > Attachments: tobenj.txt > > > I thought this was working. Unfortunately, a product I was trying to use > wanted to run with Maven 1.0.2 so I downloaded and installed it. But I > changed all the settings I can find back to Maven 2. > Now, I am trying to do a simple mvn clean install but I get errors no matter > what. > Is there a simple way to clean up everything and start over? > Special circumstances. > I have tried > creating a new .m2 directory > Settings: > M2=C:\cygwin\usr\local\maven\apache-maven-2.0.9\bin > M2_HOME=C:\cygwin\usr\local\maven\apache-maven-2.0.9 > MAVEN_OPTS=-XX:MaxPermSize=128m -Xmx512m > I am trying this under CMD and under Cygwin. > Here's what I get. > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'archetype'. > [INFO] org.apache.maven.plugins: checking for updates from central > [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be > retrieved from repository: central due to an > error: Error transferring file > [INFO] Repository 'central' will be blacklisted > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not > exist or no valid version could be found > [INFO] > > [INFO] For more information, run Maven with the -e switch -- 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: (MANTTASKS-87) Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml will cause a "Error downloading parent pom" error
[
http://jira.codehaus.org/browse/MANTTASKS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152348#action_152348
]
bbrouwer edited comment on MANTTASKS-87 at 10/29/08 3:33 PM:
--
I think I have a problem that is related to this issue as well. If I have a pom
that lists a parent pom using in the pom.xml, it seems that it
ignores the relativePath and only looks in the local repository for the parent
pom. I have gotten around this problem in my build script by doing this:
{code:xml}
{code}
But it doesn't seem right that I should be required to do this.
{code:xml|title=build.xml}
{code}
{code:xml|title=pom.xml}
4.0.0
com.gfs.test
main
com.gfs.test
parent
1.0.0
./parent-pom.xml
jar
1.0.0
{code}
{code:xml|title=parent-pom.xml}
4.0.0
com.gfs.test
parent
pom
1.0.0
{code}
was (Author: bbrouwer):
I think I have a problem that is related to this issue as well. If I have a
pom that lists a parent pom using in the pom.xml, it seems that
it ignores the relativePath and only looks in the local repository for the
parent pom. I have gotten around this problem in my build script by doing this:
{code:xml}
{code}
But it doesn't seem right that I should be required to do this.
{code:xml|title=build.xml}
{code}
{code:xml|title=pom.xml}
4.0.0
com.gfs.test
main
com.gfs.test
parent
1.0.0
./parent-pom.xml
jar
1.0.0
{code}
{code:xml|title=paremt-pom.xml}
4.0.0
com.gfs.test
parent
pom
1.0.0
{code}
> Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml
> will cause a "Error downloading parent pom" error
> -
>
> Key: MANTTASKS-87
> URL: http://jira.codehaus.org/browse/MANTTASKS-87
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Components: POM Integration
>Affects Versions: 2.0.9
> Environment: WindowsXP
> Ant version 1.7.0
>Reporter: Jeff Campbell
>Assignee: Herve Boutemy
>Priority: Blocker
> Attachments: CASE.tar.gz
>
>
> Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml
> will cause a "Error downloading parent pom" error.
> This WAS NOT a bug with version 2.0.6 of the maven-ant-tasks (new issue to
> maven-ant-tasks-2.0.7.jar and still an issue with the latest
> maven-ant-tasks-2.0.8-SNAPSHOT.jar (as of the writting of this bug)).
> Just to see if I had done something wrong with the pom.xml file I tried to
> run a Maven goal against the pom.xml file. I found that if I run "mvn clean"
> from this same directory (where the build.xml and pom.xml file is located),
> using Maven-2.0.7, I get a build successfull (it was able to find the parent
> pom.xml file... so this seems to be isolated to JUST the maven-ant-task not
> being able to find the parent pom.xml)
> Sample of the pom.xml file
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> intuit.sbconnect
> sbclogin
> 1.0.3
> SBCLogin
>
>
> mygroup
> CommonPOM
> 1.0.2
>
>
>
>
> myothergroup
> myartifact
> 1.0
>
>
>
> Line in Ant build.xml file that causes the error:
>
> Error that occurs when this line is executed in ant:
> Error downloading parent pom: Missing:
> --
> 1) mygroup:CommonPOM:pom:1.0.2
> Path to dependency:
> 1) unspecified:unspecified:jar:0.0
> 2) mygroup:CommonPOM:pom:1.0.2
> --
> 1 required artifact is missing.
> for artifact:
> unspecified:unspecified:jar:0.0
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
--
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: (MANTTASKS-87) Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml will cause a "Error downloading parent pom" error
[
http://jira.codehaus.org/browse/MANTTASKS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152348#action_152348
]
Bruce Brouwer commented on MANTTASKS-87:
I think I have a problem that is related to this issue as well. If I have a pom
that lists a parent pom using in the pom.xml, it seems that it
ignores the relativePath and only looks in the local repository for the parent
pom. I have gotten around this problem in my build script by doing this:
{code:xml}
{code}
But it doesn't seem right that I should be required to do this.
{code:xml|title=build.xml}
{code}
{code:xml|title=pom.xml}
4.0.0
com.gfs.test
main
com.gfs.test
parent
1.0.0
./parent-pom.xml
jar
1.0.0
{code}
{code:xml|title=paremt-pom.xml}
4.0.0
com.gfs.test
parent
pom
1.0.0
{code}
> Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml
> will cause a "Error downloading parent pom" error
> -
>
> Key: MANTTASKS-87
> URL: http://jira.codehaus.org/browse/MANTTASKS-87
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Components: POM Integration
>Affects Versions: 2.0.9
> Environment: WindowsXP
> Ant version 1.7.0
>Reporter: Jeff Campbell
>Assignee: Herve Boutemy
>Priority: Blocker
> Attachments: CASE.tar.gz
>
>
> Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml
> will cause a "Error downloading parent pom" error.
> This WAS NOT a bug with version 2.0.6 of the maven-ant-tasks (new issue to
> maven-ant-tasks-2.0.7.jar and still an issue with the latest
> maven-ant-tasks-2.0.8-SNAPSHOT.jar (as of the writting of this bug)).
> Just to see if I had done something wrong with the pom.xml file I tried to
> run a Maven goal against the pom.xml file. I found that if I run "mvn clean"
> from this same directory (where the build.xml and pom.xml file is located),
> using Maven-2.0.7, I get a build successfull (it was able to find the parent
> pom.xml file... so this seems to be isolated to JUST the maven-ant-task not
> being able to find the parent pom.xml)
> Sample of the pom.xml file
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> intuit.sbconnect
> sbclogin
> 1.0.3
> SBCLogin
>
>
> mygroup
> CommonPOM
> 1.0.2
>
>
>
>
> myothergroup
> myartifact
> 1.0
>
>
>
> Line in Ant build.xml file that causes the error:
>
> Error that occurs when this line is executed in ant:
> Error downloading parent pom: Missing:
> --
> 1) mygroup:CommonPOM:pom:1.0.2
> Path to dependency:
> 1) unspecified:unspecified:jar:0.0
> 2) mygroup:CommonPOM:pom:1.0.2
> --
> 1 required artifact is missing.
> for artifact:
> unspecified:unspecified:jar:0.0
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
--
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-3809) Installation simply does not work - at least as described
[
http://jira.codehaus.org/browse/MNG-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152346#action_152346
]
Benjamin Bentmann commented on MNG-3809:
You might want to check your network ("Error transferring file"). Also, without
further details ("For more information, run Maven with the -e switch"), it's
hard to help you.
> Installation simply does not work - at least as described
> -
>
> Key: MNG-3809
> URL: http://jira.codehaus.org/browse/MNG-3809
> Project: Maven 2
> Issue Type: Bug
> Components: Documentation: General, Errors, Plugin Requests, POM,
> Settings
>Affects Versions: 2.0.9
> Environment: C:\Documents and Settings\Richard Katz>mvn --version
> Maven version: 2.0.9
> Java version: 1.6.0_01
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Richard Katz
>
> I thought this was working. Unfortunately, a product I was trying to use
> wanted to run with Maven 1.0.2 so I downloaded and installed it. But I
> changed all the settings I can find back to Maven 2.
> Now, I am trying to do a simple mvn clean install but I get errors no matter
> what.
> Is there a simple way to clean up everything and start over?
> Special circumstances.
> I have tried
> creating a new .m2 directory
> Settings:
> M2=C:\cygwin\usr\local\maven\apache-maven-2.0.9\bin
> M2_HOME=C:\cygwin\usr\local\maven\apache-maven-2.0.9
> MAVEN_OPTS=-XX:MaxPermSize=128m -Xmx512m
> I am trying this under CMD and under Cygwin.
> Here's what I get.
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'archetype'.
> [INFO] org.apache.maven.plugins: checking for updates from central
> [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be
> retrieved from repository: central due to an
> error: Error transferring file
> [INFO] Repository 'central' will be blacklisted
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not
> exist or no valid version could be found
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
--
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-3809) Installation simply does not work - at least as described
Installation simply does not work - at least as described - Key: MNG-3809 URL: http://jira.codehaus.org/browse/MNG-3809 Project: Maven 2 Issue Type: Bug Components: Documentation: General, Errors, Plugin Requests, POM, Settings Affects Versions: 2.0.9 Environment: C:\Documents and Settings\Richard Katz>mvn --version Maven version: 2.0.9 Java version: 1.6.0_01 OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" Reporter: Richard Katz I thought this was working. Unfortunately, a product I was trying to use wanted to run with Maven 1.0.2 so I downloaded and installed it. But I changed all the settings I can find back to Maven 2. Now, I am trying to do a simple mvn clean install but I get errors no matter what. Is there a simple way to clean up everything and start over? Special circumstances. I have tried creating a new .m2 directory Settings: M2=C:\cygwin\usr\local\maven\apache-maven-2.0.9\bin M2_HOME=C:\cygwin\usr\local\maven\apache-maven-2.0.9 MAVEN_OPTS=-XX:MaxPermSize=128m -Xmx512m I am trying this under CMD and under Cygwin. Here's what I get. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retrieved from repository: central due to an error: Error transferring file [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch -- 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: (ARCHETYPE-191) Ability to filter filenames (rename files) during project generation
[ http://jira.codehaus.org/browse/ARCHETYPE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152337#action_152337 ] Raphaël Piéroni commented on ARCHETYPE-191: --- Frédéric, This feature is only available with the new archetype descriptor. This file is archetype-metadata.xml. Try 'mvn archetype:create-from-project' in a project Then go in target/generated-sources/archetype to see such a file. To enable the feature, please change the name of the files you have in src/main/resources/archetype-resources You can se an example of this in the test archetype like in : http://svn.apache.org/repos/asf/maven/archetype/trunk/archetype-common/src/test/archetypes/fileset-1.0/ Regards, Raphaël > Ability to filter filenames (rename files) during project generation > > > Key: ARCHETYPE-191 > URL: http://jira.codehaus.org/browse/ARCHETYPE-191 > Project: Maven Archetype > Issue Type: New Feature > Components: Generator >Affects Versions: 2.0-alpha-3 >Reporter: Wendy Smoak > Fix For: 2.0-alpha-4 > > Attachments: ReplaceAnyContextPropertyEnhancement-v2.patch, > ReplaceAnyContextPropertyEnhancement.patch > > > When generating a new project from an archetype, I need to filter not only > values within files, but the names of the files themselves. > For example, in .NET projects, the project files (.sln, .csproj) match the > name of the solution or project rather than having a fixed name like Maven's > pom.xml does. > Another user raised a similar issue on the mailing list, the ability to > filter in the name of Java source code files. > See: http://www.nabble.com/Archetype%2C-define-file-name-ts18430983.html -- 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: (MDEP-185) Dependency:copy does not work for 0 byte files
[ http://jira.codehaus.org/browse/MDEP-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Moser updated MDEP-185: --- Attachment: pom.xml a bare bones pom that displays how the problem occurs. The csv file would be the offending 0 byte file. > Dependency:copy does not work for 0 byte files > -- > > Key: MDEP-185 > URL: http://jira.codehaus.org/browse/MDEP-185 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug >Reporter: Manfred Moser >Assignee: Brian Fox > Attachments: pom.xml > > > When using dependency:copy against a file deployed to the repository with 0 > bytes the plugin reports that the artifact can not be found even if a 0 byte > file is there. Workaround of course is to make it one byte but that can cause > problems depending on what the artifact is needed for. -- 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: (MDEP-185) Dependency:copy does not work for 0 byte files
[ http://jira.codehaus.org/browse/MDEP-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152336#action_152336 ] Manfred Moser commented on MDEP-185: Btw. this issue priority should not be major IMHO .. > Dependency:copy does not work for 0 byte files > -- > > Key: MDEP-185 > URL: http://jira.codehaus.org/browse/MDEP-185 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug >Reporter: Manfred Moser >Assignee: Brian Fox > Attachments: pom.xml > > > When using dependency:copy against a file deployed to the repository with 0 > bytes the plugin reports that the artifact can not be found even if a 0 byte > file is there. Workaround of course is to make it one byte but that can cause > problems depending on what the artifact is needed for. -- 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: (ARCHETYPE-191) Ability to filter filenames (rename files) during project generation
[ http://jira.codehaus.org/browse/ARCHETYPE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152334#action_152334 ] Frederic commented on ARCHETYPE-191: I am still not able to enjoy the new feature... First, to enable it, I uderstand that i must configure the plugin against 2.0-alpha-4 in the pom of ,y archetype??? and then, I configure in my archetype.xml something like: src/main/config/setup/__artifactId__.properties but it still does not replace the token with generating the file. Any Idea? > Ability to filter filenames (rename files) during project generation > > > Key: ARCHETYPE-191 > URL: http://jira.codehaus.org/browse/ARCHETYPE-191 > Project: Maven Archetype > Issue Type: New Feature > Components: Generator >Affects Versions: 2.0-alpha-3 >Reporter: Wendy Smoak > Fix For: 2.0-alpha-4 > > Attachments: ReplaceAnyContextPropertyEnhancement-v2.patch, > ReplaceAnyContextPropertyEnhancement.patch > > > When generating a new project from an archetype, I need to filter not only > values within files, but the names of the files themselves. > For example, in .NET projects, the project files (.sln, .csproj) match the > name of the solution or project rather than having a fixed name like Maven's > pom.xml does. > Another user raised a similar issue on the mailing list, the ability to > filter in the name of Java source code files. > See: http://www.nabble.com/Archetype%2C-define-file-name-ts18430983.html -- 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: (MSHARED-78) FilteringUtils escapeWindowsPath() doesn't work on Windows
[ http://jira.codehaus.org/browse/MSHARED-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MSHARED-78: Fix Version/s: maven-filtering-1.0 Component/s: maven-filtering > FilteringUtils escapeWindowsPath() doesn't work on Windows > -- > > Key: MSHARED-78 > URL: http://jira.codehaus.org/browse/MSHARED-78 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-filtering >Affects Versions: maven-filtering-1.0-beta-2 >Reporter: Marvin Froeder > Fix For: maven-filtering-1.0 > > Attachments: FilteringUtilsTest.java > > > The method escapeWindowsPath() is replacing colon by backslash + colon. > I.e. > D:\temp > is escaped as > D\:\\temp > But windows doesn't recognize that. If you try to open D\:\\temp on > explorer, will not work. > Even java.io.File is not able to handle that too. The attached test proves > it. > I'm not sure why this backslash was add to colon, but commenting line 44 of > org.apache.maven.shared.filtering.FilteringUtils make the test work. -- 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] Moved: (MSHARED-78) FilteringUtils escapeWindowsPath() doesn't work on Windows
[ http://jira.codehaus.org/browse/MSHARED-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy moved MRESOURCES-76 to MSHARED-78: --- Affects Version/s: (was: 2.3) maven-filtering-1.0-beta-2 Issue Type: Improvement (was: Bug) Key: MSHARED-78 (was: MRESOURCES-76) Project: Maven Shared Components (was: Maven 2.x Resources Plugin) > FilteringUtils escapeWindowsPath() doesn't work on Windows > -- > > Key: MSHARED-78 > URL: http://jira.codehaus.org/browse/MSHARED-78 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-filtering >Affects Versions: maven-filtering-1.0-beta-2 >Reporter: Marvin Froeder > Fix For: maven-filtering-1.0 > > Attachments: FilteringUtilsTest.java > > > The method escapeWindowsPath() is replacing colon by backslash + colon. > I.e. > D:\temp > is escaped as > D\:\\temp > But windows doesn't recognize that. If you try to open D\:\\temp on > explorer, will not work. > Even java.io.File is not able to handle that too. The attached test proves > it. > I'm not sure why this backslash was add to colon, but commenting line 44 of > org.apache.maven.shared.filtering.FilteringUtils make the test work. -- 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: (ARCHETYPE-191) Ability to filter filenames (rename files) during project generation
[ http://jira.codehaus.org/browse/ARCHETYPE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152334#action_152334 ] frederic.tardif edited comment on ARCHETYPE-191 at 10/29/08 2:29 PM: -- I am still not able to enjoy the new feature... First, to enable it, I uderstand that i must configure the plugin against 2.0-alpha-4 in the pom of my archetype??? and then, I configure in my archetype.xml something like: src/main/config/setup/__artifactId__.properties but it still does not replace the token with generating the file. Any Idea? was (Author: frederic.tardif): I am still not able to enjoy the new feature... First, to enable it, I uderstand that i must configure the plugin against 2.0-alpha-4 in the pom of ,y archetype??? and then, I configure in my archetype.xml something like: src/main/config/setup/__artifactId__.properties but it still does not replace the token with generating the file. Any Idea? > Ability to filter filenames (rename files) during project generation > > > Key: ARCHETYPE-191 > URL: http://jira.codehaus.org/browse/ARCHETYPE-191 > Project: Maven Archetype > Issue Type: New Feature > Components: Generator >Affects Versions: 2.0-alpha-3 >Reporter: Wendy Smoak > Fix For: 2.0-alpha-4 > > Attachments: ReplaceAnyContextPropertyEnhancement-v2.patch, > ReplaceAnyContextPropertyEnhancement.patch > > > When generating a new project from an archetype, I need to filter not only > values within files, but the names of the files themselves. > For example, in .NET projects, the project files (.sln, .csproj) match the > name of the solution or project rather than having a fixed name like Maven's > pom.xml does. > Another user raised a similar issue on the mailing list, the ability to > filter in the name of Java source code files. > See: http://www.nabble.com/Archetype%2C-define-file-name-ts18430983.html -- 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: (MRESOURCES-76) FilteringUtils escapeWindowsPath() doesn't work on Windows
[ http://jira.codehaus.org/browse/MRESOURCES-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152333#action_152333 ] Olivier Lamy commented on MRESOURCES-76: So what how can we fix that ? apply this only for files : *.properties ? Not really sure. > FilteringUtils escapeWindowsPath() doesn't work on Windows > -- > > Key: MRESOURCES-76 > URL: http://jira.codehaus.org/browse/MRESOURCES-76 > Project: Maven 2.x Resources Plugin > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Marvin Froeder > Attachments: FilteringUtilsTest.java > > > The method escapeWindowsPath() is replacing colon by backslash + colon. > I.e. > D:\temp > is escaped as > D\:\\temp > But windows doesn't recognize that. If you try to open D\:\\temp on > explorer, will not work. > Even java.io.File is not able to handle that too. The attached test proves > it. > I'm not sure why this backslash was add to colon, but commenting line 44 of > org.apache.maven.shared.filtering.FilteringUtils make the test work. -- 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-3762) Relocation not working for plugins
[
http://jira.codehaus.org/browse/MNG-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152330#action_152330
]
Justin Edelson commented on MNG-3762:
-
I had to revert the maven-metadata.xml file to remove the relocated version.
You can still reproduce the problem with:
mvn com.mtvi.plateng.maven:maven-hudson-plugin:2.0-alpha-2:add-job
> Relocation not working for plugins
> --
>
> Key: MNG-3762
> URL: http://jira.codehaus.org/browse/MNG-3762
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.0.9
> Environment: Maven version: 2.0.9
> Java version: 1.5.0_13
> OS name: "mac os x" version: "10.5.4" arch: "i386" Family: "unix"
>Reporter: Wendy Smoak
>
> As discussed on the user list, the relocation pom for the Jetty plugin does
> not seem to work correctly.
> See: http://www.nabble.com/Does-relocation-work-for-plugins--td19618624.html
> To reproduce, create a project from the webapp archetype, and introduce the
> Jetty plugin:
> {noformat}
>
>...
>
>
>org.mortbay.jetty
>maven-jetty-plugin
>7.0.0pre3
>
>
> {noformat}
> Attempting to build the project results in an error:
> {noformat}
> $ mvn install
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building mywebapp Maven Webapp
> [INFO]task-segment: [install]
> [INFO]
>
> Downloading:
> http://repo1.maven.org/maven2/org/mortbay/jetty/maven-jetty-plugin/7.0.0pre3/maven-jetty-plugin-7.0.0pre3.jar
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] A required plugin was not found: Plugin could not be found -
> check that the goal name is correct: Unable to download the artifact
> from any repository
> Try downloading the file manually from the project website.
> Then, install it using the command:
>mvn install:install-file -DgroupId=org.mortbay.jetty
> -DartifactId=maven-jetty-plugin -Dversion=7.0.0pre3
> -Dpackaging=maven-plugin -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there:
>mvn deploy:deploy-file -DgroupId=org.mortbay.jetty
> -DartifactId=maven-jetty-plugin -Dversion=7.0.0pre3
> -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> org.mortbay.jetty:maven-jetty-plugin:maven-plugin:7.0.0pre3
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> org.mortbay.jetty:maven-jetty-plugin:maven-plugin:7.0.0pre3
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: 1 second
> [INFO] Finished at: Mon Sep 22 19:02:01 MST 2008
> [INFO] Final Memory: 3M/7M
> [INFO]
>
> {noformat}
--
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: (MANTTASKS-87) Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml will cause a "Error downloading parent pom" error
[ http://jira.codehaus.org/browse/MANTTASKS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152318#action_152318 ] Jeremy Gustie commented on MANTTASKS-87: In my case I have non-standard local repository specified in my settings.xml file; I was able to correct the issue by specifying a value for the settingsFile attribute on the task. This option doesn't appear in the task documentation (Pom extends from AbstractArtifactTask), but it allows the task to reference the correct local repository location. > Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml > will cause a "Error downloading parent pom" error > - > > Key: MANTTASKS-87 > URL: http://jira.codehaus.org/browse/MANTTASKS-87 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: POM Integration >Affects Versions: 2.0.9 > Environment: WindowsXP > Ant version 1.7.0 >Reporter: Jeff Campbell >Assignee: Herve Boutemy >Priority: Blocker > Attachments: CASE.tar.gz > > > Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml > will cause a "Error downloading parent pom" error. > This WAS NOT a bug with version 2.0.6 of the maven-ant-tasks (new issue to > maven-ant-tasks-2.0.7.jar and still an issue with the latest > maven-ant-tasks-2.0.8-SNAPSHOT.jar (as of the writting of this bug)). > Just to see if I had done something wrong with the pom.xml file I tried to > run a Maven goal against the pom.xml file. I found that if I run "mvn clean" > from this same directory (where the build.xml and pom.xml file is located), > using Maven-2.0.7, I get a build successfull (it was able to find the parent > pom.xml file... so this seems to be isolated to JUST the maven-ant-task not > being able to find the parent pom.xml) > Sample of the pom.xml file > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > intuit.sbconnect > sbclogin > 1.0.3 > SBCLogin > > > mygroup > CommonPOM > 1.0.2 > > > > > myothergroup > myartifact > 1.0 > > > > Line in Ant build.xml file that causes the error: > > Error that occurs when this line is executed in ant: > Error downloading parent pom: Missing: > -- > 1) mygroup:CommonPOM:pom:1.0.2 > Path to dependency: > 1) unspecified:unspecified:jar:0.0 > 2) mygroup:CommonPOM:pom:1.0.2 > -- > 1 required artifact is missing. > for artifact: > unspecified:unspecified:jar:0.0 > from the specified remote repositories: > central (http://repo1.maven.org/maven2) -- 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: (MRESOURCES-76) FilteringUtils escapeWindowsPath() doesn't work on Windows
[ http://jira.codehaus.org/browse/MRESOURCES-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152316#action_152316 ] Marvin Froeder commented on MRESOURCES-76: -- I have XML and properties on my projects and it still working. I have no idea how important is to escape colon, but if this is truly required should be done only at .properties files. VELO > FilteringUtils escapeWindowsPath() doesn't work on Windows > -- > > Key: MRESOURCES-76 > URL: http://jira.codehaus.org/browse/MRESOURCES-76 > Project: Maven 2.x Resources Plugin > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Marvin Froeder > Attachments: FilteringUtilsTest.java > > > The method escapeWindowsPath() is replacing colon by backslash + colon. > I.e. > D:\temp > is escaped as > D\:\\temp > But windows doesn't recognize that. If you try to open D\:\\temp on > explorer, will not work. > Even java.io.File is not able to handle that too. The attached test proves > it. > I'm not sure why this backslash was add to colon, but commenting line 44 of > org.apache.maven.shared.filtering.FilteringUtils make the test work. -- 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: (MRESOURCES-76) FilteringUtils escapeWindowsPath() doesn't work on Windows
[ http://jira.codehaus.org/browse/MRESOURCES-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152314#action_152314 ] Benjamin Bentmann commented on MRESOURCES-76: - I believe the motivation for this escaping was the use case of filtering properties files, where backslash and colon have special meanings. > FilteringUtils escapeWindowsPath() doesn't work on Windows > -- > > Key: MRESOURCES-76 > URL: http://jira.codehaus.org/browse/MRESOURCES-76 > Project: Maven 2.x Resources Plugin > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Marvin Froeder > Attachments: FilteringUtilsTest.java > > > The method escapeWindowsPath() is replacing colon by backslash + colon. > I.e. > D:\temp > is escaped as > D\:\\temp > But windows doesn't recognize that. If you try to open D\:\\temp on > explorer, will not work. > Even java.io.File is not able to handle that too. The attached test proves > it. > I'm not sure why this backslash was add to colon, but commenting line 44 of > org.apache.maven.shared.filtering.FilteringUtils make the test work. -- 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: (MECLIPSE-273) Several resource directories with different includes and eclipse
[
http://jira.codehaus.org/browse/MECLIPSE-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152303#action_152303
]
Fredrik Wendt commented on MECLIPSE-273:
I ran across a similar example where WTP was tricked by eclipse:eclipse but mvn
package built working package artifacts (a war project):
{quote}
src/main/resources
true
filterMe.properties
src/main/resources
false
filterMe.properties
{quote}
This will generate {{}} which leads to Web Tools Project only exporting
{{filterMe.properties}} and skipping other files. The war file created in {{mvn
clean package}} on the other hand will properly include all files in
src/main/resources.
> Several resource directories with different includes and eclipse
>
>
> Key: MECLIPSE-273
> URL: http://jira.codehaus.org/browse/MECLIPSE-273
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
> (.classpath)
>Affects Versions: 2.3
>Reporter: ol
> Attachments: 113428_295.jpg
>
>
> I define the resources like this in my project :
>
>
> src/main/resources
> true
>
> p1.properties
>
>
>
> src/main/resources
> false
>
> p2.properties
>
>
>
> Then I execute the maven-eclipse-plugin to generate the .classpath and
> .project file.
> The result is not why I expected :
> - only the first resource definition is taken into account (see screenshot)
> > the file p2.properties is not copied by the eclipse build mechanism.
> Proposed solution:
> When we define 2 resource definition on the same 'directory', the
> 'maven-eclipse-plugin' should merge the includes and excludes elements.
--
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: (MANTRUN-100) Allow antrun plugin to attach artifacts to maven build
Allow antrun plugin to attach artifacts to maven build -- Key: MANTRUN-100 URL: http://jira.codehaus.org/browse/MANTRUN-100 Project: Maven 2.x Antrun Plugin Issue Type: New Feature Reporter: Paul Gier It would be useful if a jar or zip file created by the antrun plugin could be attached to the maven build lifecycle and deployed to the 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] Updated: (MNG-2446) parent Pom properties not resolved for module dependencies
[
http://jira.codehaus.org/browse/MNG-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henrik Brautaset Aronsen updated MNG-2446:
--
Attachment: InstallMojo.quoteReplacement.patch
Here's a quick fix for the Illegal group reference bug (nested properties):
[^InstallMojo.quoteReplacement.patch]
> parent Pom properties not resolved for module dependencies
> ---
>
> Key: MNG-2446
> URL: http://jira.codehaus.org/browse/MNG-2446
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 2.0.4
> Environment: WindowsXP/Linux - JDK 1.4 last version
>Reporter: Jeremie Poutrin
>Priority: Minor
> Fix For: Reviewed Pending Version Assignment
>
> Attachments: InstallMojo.quoteReplacement.patch,
> maven-version-problem.zip
>
>
> root-project --> root-pom.xml with ${my.version}
> |--->proj1 ${my.version}
> |--->proj2 ${my.version}
> | |
> | |->proj1 dependency
> |--->proj3 ${my.version}
> if I compile from the root-project directory, all compile fine.
> if I compile from the proj2 directory, maven2 resolve proj2-${my.version}
> resolve proj1-${my.version}
> but tries to resolve the parent version root-project-${my.version} but this
> is not resolved.
--
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-3057) properties not expanded in generated POMs when building A/B/C nested projects
[
http://jira.codehaus.org/browse/MNG-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henrik Brautaset Aronsen updated MNG-3057:
--
Attachment: InstallMojo.quoteReplacement.patch
Maxim: Here's a quick fix for the Illegal group reference bug (nested
properties): [^InstallMojo.quoteReplacement.patch]
> properties not expanded in generated POMs when building A/B/C nested projects
> -
>
> Key: MNG-3057
> URL: http://jira.codehaus.org/browse/MNG-3057
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 2.0.7
>Reporter: George Armhold
> Fix For: 2.0.x
>
> Attachments: example.tar.gz, generated-poms.tar.gz,
> InstallMojo.java.patch, InstallMojo.java.patch,
> InstallMojo.quoteReplacement.patch, maven-install-parent.patch
>
>
> Using Maven version: 2.0.8-SNAPSHOT, svn r547427.
> I checked out and built 2.0.8 because I was interested in Jason van Zyl's
> patch for MNG-2619- "building from the middle pom of a
> (parent,child,grandchild) heirarchy fails". The fix works for the most part,
> but there still seems to be a problem with the poms that get generated during
> the install goal. The poms that get installed into .m2/repository do not
> have properties interpolated. If I run maven like:
>$ mvn install -Dglobal-version=1.0.0
> I get poms with the string "${global-version}" embedded in the resulting poms
> rather than what I specify on the command line (or in settings.xml). The
> build works properly aside from this, and if I do "mvn help:effective-pom"
> the properties are correctly interpolated.
> I've attached a tarfile with an example A/B/C build structure that exhibits
> this behavior, as well as the generated poms.
> Many thanks for your attention.
--
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: (MNG-2446) parent Pom properties not resolved for module dependencies
[
http://jira.codehaus.org/browse/MNG-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152287#action_152287
]
henrik242 edited comment on MNG-2446 at 10/29/08 9:32 AM:
-
Sorry, I uploaded [^InstallMojo.quoteReplacement.patch] by a mistake. It
should have been attached to MNG-3057.
was (Author: henrik242):
Here's a quick fix for the Illegal group reference bug (nested properties):
[^InstallMojo.quoteReplacement.patch]
> parent Pom properties not resolved for module dependencies
> ---
>
> Key: MNG-2446
> URL: http://jira.codehaus.org/browse/MNG-2446
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 2.0.4
> Environment: WindowsXP/Linux - JDK 1.4 last version
>Reporter: Jeremie Poutrin
>Priority: Minor
> Fix For: Reviewed Pending Version Assignment
>
> Attachments: InstallMojo.quoteReplacement.patch,
> maven-version-problem.zip
>
>
> root-project --> root-pom.xml with ${my.version}
> |--->proj1 ${my.version}
> |--->proj2 ${my.version}
> | |
> | |->proj1 dependency
> |--->proj3 ${my.version}
> if I compile from the root-project directory, all compile fine.
> if I compile from the proj2 directory, maven2 resolve proj2-${my.version}
> resolve proj1-${my.version}
> but tries to resolve the parent version root-project-${my.version} but this
> is not resolved.
--
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: (MAVENUPLOAD-2253) Upload Joda-Time 1.6
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152280#action_152280 ] Stephen Colebourne commented on MAVENUPLOAD-2253: - Not really. I would need a pom.xml rather than a project.xml. Plus, I would have to generate the two signature files for every file I place there. The bundle is created by ant - I don't have to think about it. > Upload Joda-Time 1.6 > > > Key: MAVENUPLOAD-2253 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2253 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Stephen Colebourne > > http://joda-time.sourceforge.net/joda-time-1.6-bundle.jar > > http://joda-time.sourceforge.net > http://joda-time.sourceforge.net/team-list.html > > Please upload joda-time 1.6 -- 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: (MNG-3782) Variable substition not performed in transitive dependency using value from active profile
[ http://jira.codehaus.org/browse/MNG-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152274#action_152274 ] rvarttinen edited comment on MNG-3782 at 10/29/08 8:03 AM: - Attaching a patch (MyEclipseArtifactResolver.zip), addition, to m2eclipse that performs the desired result. This alteration of the code is a bit more complicated and involves two classes: - MavenProjectManagerImpl, pointing out MyEclipseArtifactResolver for instantiation instead of EclipseArtifactResolver - MyEclipseArtifactResolver with an additional method doing the variable substation prior to resolving the artifact in question. Please keep in mind that the solution in m2eclispe we have presented works for substituting variables appearing in group- or artifactId and version of an artifact to be resolved. It is not as generic as the Maven CLI patch. For us in our current project it works fine as we are about work with POM:s with variables in version fields. Somebody taking a look at this might very well find a much better, and more generic, way of doing substitution. was (Author: rvarttinen): Attaching a patch, addition, to m2eclipse that performs the desired result. This alteration of the code is a bit more complicated and involves two classes: - MavenProjectManagerImpl, pointing out MyEclipseArtifactResolver for instantiation instead of EclipseArtifactResolver - MyEclipseArtifactResolver with an additional method doing the variable substation prior to resolving the artifact in question. Please keep in mind that the solution in m2eclispe we have presented works for substituting variables appearing in group- or artifactId and version of an artifact to be resolved. It is not as generic as the Maven CLI patch. For us in our current project it works fine as we are about work with POM:s with variables in version fields. Somebody taking a look at this might very well find a much better, and more generic, way of doing substitution. > Variable substition not performed in transitive dependency using value from > active profile > -- > > Key: MNG-3782 > URL: http://jira.codehaus.org/browse/MNG-3782 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.9 > Environment: Java version: 1.6.0_07 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Robert Varttinen > Attachments: build.log, example.zip, MavenCli.java, > MyEclipseArtifactResolver.zip, settings.xml > > > When invoking the 'mvn compile' command and a profile is active, defined in > settings.xml, a variable substitution is not performed in a transitive > dependency. > In the example provided the project to be built, C, depends on B which in its > turn depends on A. The versions of B and A to be used are defined in a > profile, the POM-files defines a variable indicating the versions. The > profile in question is defined in the settings.xml and is always active > (check with command 'mvn help:active-profiles'). The results of project A and > B are successfully built and installed in the local repository. > Invoking a build for project C using a command line parameter indicating, > 'mvn compile -Dparentversion=0.0.1-SNAPSHOT, the versions render a successful > build. The transitive dependency is resolved correctly. > This problem is also visible in Eclipse, m2eclipse, as the project C in the > example provided, does not build (error indication). The example provided > includes Eclipse projects displaying this (version 0.9.7.20081001-2217 of the > Eclipse plugin is used). > The settings.xml and a build log are provided as attachments to this issue. -- 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-3782) Variable substition not performed in transitive dependency using value from active profile
[ http://jira.codehaus.org/browse/MNG-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Varttinen updated MNG-3782: -- Attachment: MyEclipseArtifactResolver.zip Attaching a patch, addition, to m2eclipse that performs the desired result. This alteration of the code is a bit more complicated and involves two classes: - MavenProjectManagerImpl, pointing out MyEclipseArtifactResolver for instantiation instead of EclipseArtifactResolver - MyEclipseArtifactResolver with an additional method doing the variable substation prior to resolving the artifact in question. Please keep in mind that the solution in m2eclispe we have presented works for substituting variables appearing in group- or artifactId and version of an artifact to be resolved. It is not as generic as the Maven CLI patch. For us in our current project it works fine as we are about work with POM:s with variables in version fields. Somebody taking a look at this might very well find a much better, and more generic, way of doing substitution. > Variable substition not performed in transitive dependency using value from > active profile > -- > > Key: MNG-3782 > URL: http://jira.codehaus.org/browse/MNG-3782 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.9 > Environment: Java version: 1.6.0_07 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Robert Varttinen > Attachments: build.log, example.zip, MavenCli.java, > MyEclipseArtifactResolver.zip, settings.xml > > > When invoking the 'mvn compile' command and a profile is active, defined in > settings.xml, a variable substitution is not performed in a transitive > dependency. > In the example provided the project to be built, C, depends on B which in its > turn depends on A. The versions of B and A to be used are defined in a > profile, the POM-files defines a variable indicating the versions. The > profile in question is defined in the settings.xml and is always active > (check with command 'mvn help:active-profiles'). The results of project A and > B are successfully built and installed in the local repository. > Invoking a build for project C using a command line parameter indicating, > 'mvn compile -Dparentversion=0.0.1-SNAPSHOT, the versions render a successful > build. The transitive dependency is resolved correctly. > This problem is also visible in Eclipse, m2eclipse, as the project C in the > example provided, does not build (error indication). The example provided > includes Eclipse projects displaying this (version 0.9.7.20081001-2217 of the > Eclipse plugin is used). > The settings.xml and a build log are provided as attachments to this issue. -- 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: (MRESOURCES-76) FilteringUtils escapeWindowsPath() doesn't work on Windows
[ http://jira.codehaus.org/browse/MRESOURCES-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marvin Froeder updated MRESOURCES-76: - Affects Version/s: 2.3 > FilteringUtils escapeWindowsPath() doesn't work on Windows > -- > > Key: MRESOURCES-76 > URL: http://jira.codehaus.org/browse/MRESOURCES-76 > Project: Maven 2.x Resources Plugin > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Marvin Froeder > Attachments: FilteringUtilsTest.java > > > The method escapeWindowsPath() is replacing colon by backslash + colon. > I.e. > D:\temp > is escaped as > D\:\\temp > But windows doesn't recognize that. If you try to open D\:\\temp on > explorer, will not work. > Even java.io.File is not able to handle that too. The attached test proves > it. > I'm not sure why this backslash was add to colon, but commenting line 44 of > org.apache.maven.shared.filtering.FilteringUtils make the test work. -- 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: (MRESOURCES-76) FilteringUtils escapeWindowsPath() doesn't work on Windows
FilteringUtils escapeWindowsPath() doesn't work on Windows -- Key: MRESOURCES-76 URL: http://jira.codehaus.org/browse/MRESOURCES-76 Project: Maven 2.x Resources Plugin Issue Type: Bug Reporter: Marvin Froeder Attachments: FilteringUtilsTest.java The method escapeWindowsPath() is replacing colon by backslash + colon. I.e. D:\temp is escaped as D\:\\temp But windows doesn't recognize that. If you try to open D\:\\temp on explorer, will not work. Even java.io.File is not able to handle that too. The attached test proves it. I'm not sure why this backslash was add to colon, but commenting line 44 of org.apache.maven.shared.filtering.FilteringUtils make the test work. -- 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: (MNG-3782) Variable substition not performed in transitive dependency using value from active profile
[ http://jira.codehaus.org/browse/MNG-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152269#action_152269 ] rvarttinen edited comment on MNG-3782 at 10/29/08 7:34 AM: - The uploaded file (MavenCli.java) has an altered version of MavenCli, it has a piece of code added to a section of the main(...) method. The "patch" passed the properties of an active profile to the system properties. Thus, in our case, we get a variable substitution performed accordingly. This can, however, also be performed by passing the properties in question using the '-D..' option on the command line. This might be a problem though when invoked from an automatic build tool. was (Author: rvarttinen): This is an altered version of MavenCli, it has a piece of code added to a section of the main(...) method. The "patch" passed the properties of an active profile to the system properties. Thus, in our case, we get a variable substitution performed accordingly. This can, however, also be performed by passing the properties in question using the '-D..' option on the command line. This might be a problem though when invoked from an automatic build tool. > Variable substition not performed in transitive dependency using value from > active profile > -- > > Key: MNG-3782 > URL: http://jira.codehaus.org/browse/MNG-3782 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.9 > Environment: Java version: 1.6.0_07 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Robert Varttinen > Attachments: build.log, example.zip, MavenCli.java, settings.xml > > > When invoking the 'mvn compile' command and a profile is active, defined in > settings.xml, a variable substitution is not performed in a transitive > dependency. > In the example provided the project to be built, C, depends on B which in its > turn depends on A. The versions of B and A to be used are defined in a > profile, the POM-files defines a variable indicating the versions. The > profile in question is defined in the settings.xml and is always active > (check with command 'mvn help:active-profiles'). The results of project A and > B are successfully built and installed in the local repository. > Invoking a build for project C using a command line parameter indicating, > 'mvn compile -Dparentversion=0.0.1-SNAPSHOT, the versions render a successful > build. The transitive dependency is resolved correctly. > This problem is also visible in Eclipse, m2eclipse, as the project C in the > example provided, does not build (error indication). The example provided > includes Eclipse projects displaying this (version 0.9.7.20081001-2217 of the > Eclipse plugin is used). > The settings.xml and a build log are provided as attachments to this issue. -- 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-3782) Variable substition not performed in transitive dependency using value from active profile
[ http://jira.codehaus.org/browse/MNG-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Varttinen updated MNG-3782: -- Attachment: MavenCli.java This is an altered version of MavenCli, it has a piece of code added to a section of the main(...) method. The "patch" passed the properties of an active profile to the system properties. Thus, in our case, we get a variable substitution performed accordingly. This can, however, also be performed by passing the properties in question using the '-D..' option on the command line. This might be a problem though when invoked from an automatic build tool. > Variable substition not performed in transitive dependency using value from > active profile > -- > > Key: MNG-3782 > URL: http://jira.codehaus.org/browse/MNG-3782 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.9 > Environment: Java version: 1.6.0_07 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Robert Varttinen > Attachments: build.log, example.zip, MavenCli.java, settings.xml > > > When invoking the 'mvn compile' command and a profile is active, defined in > settings.xml, a variable substitution is not performed in a transitive > dependency. > In the example provided the project to be built, C, depends on B which in its > turn depends on A. The versions of B and A to be used are defined in a > profile, the POM-files defines a variable indicating the versions. The > profile in question is defined in the settings.xml and is always active > (check with command 'mvn help:active-profiles'). The results of project A and > B are successfully built and installed in the local repository. > Invoking a build for project C using a command line parameter indicating, > 'mvn compile -Dparentversion=0.0.1-SNAPSHOT, the versions render a successful > build. The transitive dependency is resolved correctly. > This problem is also visible in Eclipse, m2eclipse, as the project C in the > example provided, does not build (error indication). The example provided > includes Eclipse projects displaying this (version 0.9.7.20081001-2217 of the > Eclipse plugin is used). > The settings.xml and a build log are provided as attachments to this issue. -- 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: (SCM-424) Provide a way of setting password for ext connections using internal ssh code
Provide a way of setting password for ext connections using internal ssh code - Key: SCM-424 URL: http://jira.codehaus.org/browse/SCM-424 Project: Maven SCM Issue Type: New Feature Components: maven-scm-provider-cvs Environment: Any Reporter: Klaus Brunner ExtConnection apparently has all the necessary stuff in place to initiate an "ext using ssh" connection on its own, without an external ssh command. However, there seems to be no way of setting the password for such connections: ext URLs are fixed to 4 tokens so you can set a username, but not a password (see AbstractCvsScmProvider - not misleading message that there are "too few tokens" when in fact there may be too many). It's also not retrieved from a system property or such - so it's always "password is null", whatever you do. Suggestion: try to get the SSH password from a System property. -- 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: (SCM-132) extssh connection method not shown
[ http://jira.codehaus.org/browse/SCM-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152264#action_152264 ] Klaus Brunner commented on SCM-132: --- "extssh" is simply Eclipse's way of saying "ext using ssh as the external rsh". As far as I understand the Maven SCM code, using "ext" actually defaults to trying an ssh connection anyway: see CvsConnection.connect() and the ExtConnection class which uses a Java ssh library when no rsh is explicitly set. So ext is extssh in fact, unless CVS_RSH is set to point to something else. What's annoying is that there is apparently no way of setting the password (an SCM url with "ext" doesn't allow adding the password, and it seems it's not retrieved any other way). > extssh connection method not shown > -- > > Key: SCM-132 > URL: http://jira.codehaus.org/browse/SCM-132 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-cvs > Environment: Windows 2000; Java 1.4 JDK, Maven 2.01 maven-scm-plugin > 1.0-alpha-2 >Reporter: Todd Nine > Fix For: future > > > When attemping to perform a release from a project checked out from eclipse I > receive the following error. > [INFO] [release:prepare] > [INFO] Verifying there are no local modifications ... > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] An error is occurred in the status process. > Embedded error: Error! > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred > in the status process. > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:485) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:455) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:216) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.MojoExecutionException: An error is > occurred in the status process. > at > org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModifications(PrepareReleaseMojo.java:514) > at > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:201) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:432) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:530) > ... 16 more > Caused by: org.apache.maven.scm.ScmException: Error! > at > org.apache.maven.plugins.release.helpers.ScmHelper.checkResult(ScmHelper.java:124) > at > org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelper.java:175) > at > org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModifications(PrepareReleaseMojo.java:510) > ... 19 more > Since Eclipse is a commonly used IDE, is it possible to add the extssh > connection parameter. Below is my scm from my pom.xml > > scm:cvs:ext:[EMAIL > PROTECTED]:/a01/proj/CVS:webservices/ServiceProviders > scm:cvs:ext:[EMAIL > PROTECTED]:/a01/proj/CVS:webservices/ServiceProviders > HEAD > > http://empt.ata.com/cgi-bin/cvsweb.cgi/webservices/ServiceProviders/?cvsroot=ATA.com-Development > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.or
[jira] Created: (MDEPLOY-88) Artifacts with invalid id can be deployed with deploy:deploy-file.
Artifacts with invalid id can be deployed with deploy:deploy-file.
--
Key: MDEPLOY-88
URL: http://jira.codehaus.org/browse/MDEPLOY-88
Project: Maven 2.x Deploy Plugin
Issue Type: Bug
Affects Versions: 2.4
Reporter: Joerg Schaible
Real world example: WebLogic delivers webserviceclient+ssl.jar.
It is no problem to create a POM file for this artifact with as
"weblogic:webserviceclient+ssl:9.2.1.0" and deploy this with the prepared POM
into the repository. It is also no problem to deploy artifacts with a prepared
POM that declare a dependency to this artifact. However, if this artifact is
declared as direct dependency to a project the build fails immediately with :
{noformat}
Validation Messages:
[0] 'dependencies.dependency.artifactId' with value 'webserviceclient+ssl'
does not match a valid id pattern.
{noformat}
and worse, if the artifact is a transitive dep, you only get a non-explaining
warning and all other dependencies of the "transitive artifact" are dropped:
{noformat}
[WARNING] POM for 'com.company:artifact-name:pom:47.11:runtime' is invalid. It
will be ignored for artifact resolution. Reason: F
ailed to validate POM for project com.company:artifact-name at Artifact
[com.company:artifact-name:pom:47.11:runtime]
{noformat}
The deploy plugin has to validate the (also a generated) POM before deploying
an artifact with deploy:deploy-file.
BTW: I suppose the install plugin has the same issue with install:install-file.
However, I also suppose the code is shared ;-)
--
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-2255) JFlex 1.3.5
JFlex 1.3.5
---
Key: MAVENUPLOAD-2255
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2255
Project: Maven Upload Requests
Issue Type: Wish
Reporter: Grzegorz Slowikowski
Attachments: jflex-1.3.5-bundle.jar
Old version of JFlex. Pom copied from 1.4.2 version
(http://jira.codehaus.org/browse/MAVENUPLOAD-2086). No change, except
${project.version}. I built the project from sources using this pom. Everything
OK.
--
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-3805) Ordering of extension class path is indeterministic
[ http://jira.codehaus.org/browse/MNG-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-3805. - Assignee: Brett Porter Resolution: Fixed Fix Version/s: 2.0.10 Applied and re-instated the IT > Ordering of extension class path is indeterministic > --- > > Key: MNG-3805 > URL: http://jira.codehaus.org/browse/MNG-3805 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Dependencies >Affects Versions: 2.0.9, 2.1.0-M1 >Reporter: Benjamin Bentmann >Assignee: Brett Porter > Fix For: 2.0.10 > > Attachments: deterministic-dependency-ordering.patch, log-bad.txt, > log-good.txt > > > One part of Maven where class path ordering hasn't already been fixed in the > past is the extension class path. Apart from a proposed patch, two logs from > our IT testmng3599useHttpProxyForWebDAV are attached. Both were run against > Maven 2.0.10-RC1, with the only difference being one using JDK 1.4 and the > other one 1.6. Not only do these logs substantially differ, the build on JDK > 1.6 even fails due to picking up the wrong extension classes. -- 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-3599) webdav does not set http-proxy correctly
[ http://jira.codehaus.org/browse/MNG-3599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-3599: -- Fix Version/s: 2.0.10 > webdav does not set http-proxy correctly > > > Key: MNG-3599 > URL: http://jira.codehaus.org/browse/MNG-3599 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.9 >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 2.0.10, 2.1.0-M1 > > Attachments: MNG-3599.patch, webdav.log > > > patch is attached to WAGON-82 > (0001-Make-the-artifact-manager-using-wagons-ProxyInfoProv.patch), utilising > the new APIs in beta-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
