[jira] Created: (MAVENUPLOAD-2118) Please sync net.sf.gwt-widget groupId with central
Please sync net.sf.gwt-widget groupId with central -- Key: MAVENUPLOAD-2118 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2118 Project: Maven Upload Requests Issue Type: Wish Reporter: nicolas de loof -- 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: (JXR-12) Allow filtering of links to javadocs
[ http://jira.codehaus.org/browse/JXR-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139283#action_139283 ] Anders Hammar commented on JXR-12: -- If implementing this, please make it flexible. Alternative a) does not provide for the reality of public class that are not part of a public API (impl classes for instance). Alternative b) would be great, but an easier alterantive could be to provide for the possibility of specifying the packages to exclude. > Allow filtering of links to javadocs > > > Key: JXR-12 > URL: http://jira.codehaus.org/browse/JXR-12 > Project: Maven JXR > Issue Type: Improvement > Components: jxr > Environment: Any. >Reporter: Oscar Picasso > > Suppose: > 1- I want to generate javadocs only for my project API (only public classes > and interfaces). > 2- As a convenience for developers willing to collaborate on the project, I > would like to generate browsable source for public and package private > classes and methods. > (1) is mainly targeted at people using the project. > (2) is mainly targeted at people working on the project. > Currently jxr generates links for javadocs whether they exist or not. So > links to packages private class javadocs are broken. > I would be nice to: > a- Be able to filter links to javadocs bases on the public / package private > properties of the classes. > even better > b- generate javadoc links, only to existing javadocs. -- 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: (SUREFIRE-503) Parent pom settings not overridden
Parent pom settings not overridden -- Key: SUREFIRE-503 URL: http://jira.codehaus.org/browse/SUREFIRE-503 Project: Maven Surefire Issue Type: Bug Components: plugin Affects Versions: 2.4.2 Environment: Windows XP SP2, Maven 2.0.9 Reporter: Paul Grove In my team parent pom from which all projects inherit I have this in the pom org.apache.maven.plugins maven-surefire-plugin **/*ITest.java org.apache.maven.plugins maven-surefire-plugin surefire-it integration-test test none **/*ITest.java In my project pom I was to add some more exclusions and inclusions so I added this org.apache.maven.plugins maven-surefire-plugin **/functest/** **/perftest/** org.apache.maven.plugins maven-surefire-plugin surefire-it integration-test test none **/functest/** **/perftest/** But when I run mvn test all the tests in functest and perftest package still run. but if I add the exclusions and inclusions to the team parent pom it works as expected so I am a bit confused. -- 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: (SUREFIRE-503) Parent pom settings not overridden
[ http://jira.codehaus.org/browse/SUREFIRE-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139300#action_139300 ] paulg edited comment on SUREFIRE-503 at 6/23/08 5:46 AM: -- The includes and excludes do have two stars ** the editor stripped them out and made the text bold must be some sort of wiki markup processing!! was (Author: paulg): The includes and excludes do have to stars ** the editor sripped them out and made the text bold must be some sort of wiki markup processing!! > Parent pom settings not overridden > -- > > Key: SUREFIRE-503 > URL: http://jira.codehaus.org/browse/SUREFIRE-503 > Project: Maven Surefire > Issue Type: Bug > Components: plugin >Affects Versions: 2.4.2 > Environment: Windows XP SP2, Maven 2.0.9 >Reporter: Paul Grove > > In my team parent pom from which all projects inherit I have this in the pom > > > > org.apache.maven.plugins > maven-surefire-plugin > > > > **/*ITest.java > > > > > org.apache.maven.plugins > maven-surefire-plugin > > > surefire-it > integration-test > > test > > > > > none > > > > **/*ITest.java > > > > > > > > In my project pom I was to add some more exclusions and inclusions so I added > this > > > > org.apache.maven.plugins > maven-surefire-plugin > > > > **/functest/** > > **/perftest/** > > > > > org.apache.maven.plugins > maven-surefire-plugin > > > surefire-it > integration-test > > test > > > > > none > > > > **/functest/** > > **/perftest/** > > > > > > > > But when I run mvn test all the tests in functest and perftest package still > run. but if I add the exclusions and inclusions to the team parent pom it > works as expected so I am a bit confused. -- 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: (SUREFIRE-503) Parent pom settings not overridden
[ http://jira.codehaus.org/browse/SUREFIRE-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139300#action_139300 ] Paul Grove commented on SUREFIRE-503: - The includes and excludes do have to stars ** the editor sripped them out and made the text bold must be some sort of wiki markup processing!! > Parent pom settings not overridden > -- > > Key: SUREFIRE-503 > URL: http://jira.codehaus.org/browse/SUREFIRE-503 > Project: Maven Surefire > Issue Type: Bug > Components: plugin >Affects Versions: 2.4.2 > Environment: Windows XP SP2, Maven 2.0.9 >Reporter: Paul Grove > > In my team parent pom from which all projects inherit I have this in the pom > > > > org.apache.maven.plugins > maven-surefire-plugin > > > > **/*ITest.java > > > > > org.apache.maven.plugins > maven-surefire-plugin > > > surefire-it > integration-test > > test > > > > > none > > > > **/*ITest.java > > > > > > > > In my project pom I was to add some more exclusions and inclusions so I added > this > > > > org.apache.maven.plugins > maven-surefire-plugin > > > > **/functest/** > > **/perftest/** > > > > > org.apache.maven.plugins > maven-surefire-plugin > > > surefire-it > integration-test > > test > > > > > none > > > > **/functest/** > > **/perftest/** > > > > > > > > But when I run mvn test all the tests in functest and perftest package still > run. but if I add the exclusions and inclusions to the team parent pom it > works as expected so I am a bit confused. -- 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: (MCOMPILER-77) Build stops an warning "WARNUNG: Duplicate name in Manifest: Depends-On."
Build stops an warning "WARNUNG: Duplicate name in Manifest: Depends-On."
-
Key: MCOMPILER-77
URL: http://jira.codehaus.org/browse/MCOMPILER-77
Project: Maven 2.x Compiler Plugin
Issue Type: Bug
Affects Versions: 2.0.2
Environment: Windws XP / maven 2.0.9
Reporter: Andreas Schneider
I am configuring the plugin :
org.apache.maven.plugins
maven-compiler-plugin
true
${JAVA_1_6_HOME}/bin/javac
1.6
false
false
I get a warning
WARNUNG: Duplicate name in Manifest: Depends-On.
Ensure that the manifest does not have duplicate entries,
and the build fails.
If I don't configure the plugin and I set my JAVA_HOME to JAVA_1_6_HOME
everything is working fine. I would expect the same behavior.
--
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-3627) Maven complains for the lack of a test dependency even when skipping tests
Maven complains for the lack of a test dependency even when skipping tests
--
Key: MNG-3627
URL: http://jira.codehaus.org/browse/MNG-3627
Project: Maven 2
Issue Type: Bug
Components: Dependencies
Affects Versions: 2.0.9
Reporter: Andrea Aime
Trying to build GeoServer trunk without tests (-Dmaven.test.skip=true) we're
getting an error message stating that some jars marked as test dependencies are
not found. In particular, these are the tests jar of another module in the
build, which is not getting built because of the test.skip setting and it's not
already available on the repository.
Yet mvn dependency:tree does report the following:
{panel}
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'dependency'.
[INFO]
[INFO] Building Web Coverage Service 1.1.1 Module
[INFO]task-segment: [dependency:tree]
[INFO]
[INFO] [dependency:tree]
[INFO] org.geoserver:wcs1_1:jar:1.8.0-SNAPSHOT
[INFO] +- org.geoserver:main:jar:1.8.0-SNAPSHOT:compile
[INFO] | +- org.geoserver:data:jar:1.8.0-SNAPSHOT:compile
[INFO] | | +- org.geoserver:platform:jar:1.8.0-SNAPSHOT:compile
[INFO] | | | +- javax.media:jai_core:jar:1.1.3:compile
[INFO] | | | +- javax.media:jai_codec:jar:1.1.3:compile
[INFO] | | | \- javax.media:jai_imageio:jar:1.1:compile
[INFO] | | +- org.geotools:gt-epsg-hsql:jar:2.5-SNAPSHOT:compile
[INFO] | | +- org.geotools:gt-h2:jar:2.5-SNAPSHOT:compile
[INFO] | | | +- org.h2database:h2:jar:1.0-SNAPSHOT:compile
[INFO] | | | +- org.openplans:spatialdbbox:jar:1.0-SNAPSHOT:compile
[INFO] | | | \- mysql:mysql-connector-java:jar:5.1.5:compile
[INFO] | | +- org.geotools:gt-property:jar:2.5-SNAPSHOT:compile
[INFO] | | +- org.geotools.xsd:gt-xsd-gml2:jar:2.5-SNAPSHOT:compile
[INFO] | | \- xml-apis:xml-apis-xerces:jar:2.7.1:compile
[INFO] | +- org.geoserver:ows:jar:1.8.0-SNAPSHOT:compile
[INFO] | | +- org.acegisecurity:acegi-security:jar:1.0.3:compile
[INFO] | | | +- org.springframework:spring-jdbc:jar:2.5.2:compile (version
managed from 1.2.8)
[INFO] | | | | \- org.springframework:spring-tx:jar:2.5.2:compile
[INFO] | | | \- commons-codec:commons-codec:jar:1.3:compile
[INFO] | | +- commons-lang:commons-lang:jar:2.1:compile
[INFO] | | +- org.geotools.xsd:gt-xsd-core:jar:2.5-SNAPSHOT:compile
[INFO] | | \- xpp3:xpp3:jar:1.1.3.4.O:compile
[INFO] | +- javax.servlet:servlet-api:jar:2.4:compile
[INFO] | +- org.restlet:org.restlet:jar:1.0.8:compile (version managed from
1.0.5)
[INFO] | +- org.restlet:org.restlet.ext.freemarker:jar:1.0.8:compile (version
managed from 1.0.5)
[INFO] | +-
com.noelios.restlet:com.noelios.restlet.ext.servlet:jar:1.0.8:compile (version
managed from 1.0.5)
[INFO] | | \- com.noelios.restlet:com.noelios.restlet:jar:1.0.8:compile
[INFO] | +- net.sf.json-lib:json-lib:jar:jdk13:2.1:compile
[INFO] | | +- commons-collections:commons-collections:jar:3.1:compile
[INFO] | | \- net.sf.ezmorph:ezmorph:jar:1.0.3:compile
[INFO] | +- struts:struts:jar:1.2.9:compile
[INFO] | | \- antlr:antlr:jar:2.7.2:compile
[INFO] | +- xml-apis:xml-apis:jar:1.0.b2:compile
[INFO] | +- xerces:xercesImpl:jar:2.6.2:compile
[INFO] | +- xalan:xalan:jar:2.7.0:compile
[INFO] | +- commons-beanutils:commons-beanutils:jar:1.7.0:compile
[INFO] | +- commons-digester:commons-digester:jar:1.7:compile
[INFO] | +- commons-fileupload:commons-fileupload:jar:1.2.1:compile
[INFO] | +- commons-io:commons-io:jar:1.3.2:compile
[INFO] | +- commons-httpclient:commons-httpclient:jar:2.0:compile
[INFO] | +- commons-validator:commons-validator:jar:1.1.4:compile
[INFO] | +- org.freemarker:freemarker:jar:2.3.13:compile
[INFO] | +- oro:oro:jar:2.0.8:compile
[INFO] | +- org.geotools:gt-cql:jar:2.5-SNAPSHOT:compile
[INFO] | +- log4j:log4j:jar:1.2.14:compile
[INFO] | +- org.geotools:gt-coverage:jar:2.5-SNAPSHOT:compile
[INFO] | +- org.geotools:gt-validation:jar:2.5-SNAPSHOT:compile
[INFO] | | \- org.geotools:gt-graph:jar:2.5-SNAPSHOT:compile
[INFO] | +- org.geotools:gt-data:jar:2.5-SNAPSHOT:compile
[INFO] | +- org.geotools:gt-jdbc:jar:2.5-SNAPSHOT:compile
[INFO] | | \- commons-dbcp:commons-dbcp:jar:1.2.2:compile
[INFO] | +- org.geotools:gt-metadata:jar:2.5-SNAPSHOT:compile
[INFO] | | +- java3d:vecmath:jar:1.3.1:compile
[INFO] | | +- org.opengis:geoapi:jar:2.2-SNAPSHOT:compile
[INFO] | | \- net.java.dev.jsr-275:jsr-275:jar:1.0-beta-2:compile
[INFO] | +- org.springframework:spring-aop:jar:2.5.2:compile
[INFO] | \- com.thoughtworks.xstream:xstream:jar:1.3:compile
[INFO] | \- xpp3:xpp3_min:jar:1.1.4c:compile
[INFO] +- org.geotools.ogc:net.opengis.wcs:jar:2.5-SNAPSHOT:compile
[INFO] | +- org.geotools.ogc:net.opengis.ows:jar:2.5-SNAPSHOT:compil
[jira] Commented: (MNG-3627) Maven complains for the lack of a test dependency even when skipping tests
[
http://jira.codehaus.org/browse/MNG-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139313#action_139313
]
Benjamin Bentmann commented on MNG-3627:
bq. so why complian if they are not around?
Skipping tests is a feature of the Compiler/Surefire plugin, not Maven. That is
to say, these plugins are always executed (e.g. it's them who print "Skipping"
on the console) and it's on their discretion to skip the tests by simply
quitting their executions. Now, when the plugins are executed, Maven has
already resolved the dependencies the plugin requires. That is, dependency
resolution is performed by the Maven core beforehand and happens
unconditionally, without considering any option of a particular plugin.
> Maven complains for the lack of a test dependency even when skipping tests
> --
>
> Key: MNG-3627
> URL: http://jira.codehaus.org/browse/MNG-3627
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 2.0.9
>Reporter: Andrea Aime
>
> Trying to build GeoServer trunk without tests (-Dmaven.test.skip=true) we're
> getting an error message stating that some jars marked as test dependencies
> are not found. In particular, these are the tests jar of another module in
> the build, which is not getting built because of the test.skip setting and
> it's not already available on the repository.
> Yet mvn dependency:tree does report the following:
> {panel}
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'dependency'.
> [INFO]
>
> [INFO] Building Web Coverage Service 1.1.1 Module
> [INFO]task-segment: [dependency:tree]
> [INFO]
>
> [INFO] [dependency:tree]
> [INFO] org.geoserver:wcs1_1:jar:1.8.0-SNAPSHOT
> [INFO] +- org.geoserver:main:jar:1.8.0-SNAPSHOT:compile
> [INFO] | +- org.geoserver:data:jar:1.8.0-SNAPSHOT:compile
> [INFO] | | +- org.geoserver:platform:jar:1.8.0-SNAPSHOT:compile
> [INFO] | | | +- javax.media:jai_core:jar:1.1.3:compile
> [INFO] | | | +- javax.media:jai_codec:jar:1.1.3:compile
> [INFO] | | | \- javax.media:jai_imageio:jar:1.1:compile
> [INFO] | | +- org.geotools:gt-epsg-hsql:jar:2.5-SNAPSHOT:compile
> [INFO] | | +- org.geotools:gt-h2:jar:2.5-SNAPSHOT:compile
> [INFO] | | | +- org.h2database:h2:jar:1.0-SNAPSHOT:compile
> [INFO] | | | +- org.openplans:spatialdbbox:jar:1.0-SNAPSHOT:compile
> [INFO] | | | \- mysql:mysql-connector-java:jar:5.1.5:compile
> [INFO] | | +- org.geotools:gt-property:jar:2.5-SNAPSHOT:compile
> [INFO] | | +- org.geotools.xsd:gt-xsd-gml2:jar:2.5-SNAPSHOT:compile
> [INFO] | | \- xml-apis:xml-apis-xerces:jar:2.7.1:compile
> [INFO] | +- org.geoserver:ows:jar:1.8.0-SNAPSHOT:compile
> [INFO] | | +- org.acegisecurity:acegi-security:jar:1.0.3:compile
> [INFO] | | | +- org.springframework:spring-jdbc:jar:2.5.2:compile (version
> managed from 1.2.8)
> [INFO] | | | | \- org.springframework:spring-tx:jar:2.5.2:compile
> [INFO] | | | \- commons-codec:commons-codec:jar:1.3:compile
> [INFO] | | +- commons-lang:commons-lang:jar:2.1:compile
> [INFO] | | +- org.geotools.xsd:gt-xsd-core:jar:2.5-SNAPSHOT:compile
> [INFO] | | \- xpp3:xpp3:jar:1.1.3.4.O:compile
> [INFO] | +- javax.servlet:servlet-api:jar:2.4:compile
> [INFO] | +- org.restlet:org.restlet:jar:1.0.8:compile (version managed from
> 1.0.5)
> [INFO] | +- org.restlet:org.restlet.ext.freemarker:jar:1.0.8:compile
> (version managed from 1.0.5)
> [INFO] | +-
> com.noelios.restlet:com.noelios.restlet.ext.servlet:jar:1.0.8:compile
> (version managed from 1.0.5)
> [INFO] | | \- com.noelios.restlet:com.noelios.restlet:jar:1.0.8:compile
> [INFO] | +- net.sf.json-lib:json-lib:jar:jdk13:2.1:compile
> [INFO] | | +- commons-collections:commons-collections:jar:3.1:compile
> [INFO] | | \- net.sf.ezmorph:ezmorph:jar:1.0.3:compile
> [INFO] | +- struts:struts:jar:1.2.9:compile
> [INFO] | | \- antlr:antlr:jar:2.7.2:compile
> [INFO] | +- xml-apis:xml-apis:jar:1.0.b2:compile
> [INFO] | +- xerces:xercesImpl:jar:2.6.2:compile
> [INFO] | +- xalan:xalan:jar:2.7.0:compile
> [INFO] | +- commons-beanutils:commons-beanutils:jar:1.7.0:compile
> [INFO] | +- commons-digester:commons-digester:jar:1.7:compile
> [INFO] | +- commons-fileupload:commons-fileupload:jar:1.2.1:compile
> [INFO] | +- commons-io:commons-io:jar:1.3.2:compile
> [INFO] | +- commons-httpclient:commons-httpclient:jar:2.0:compile
> [INFO] | +- commons-validator:commons-validator:jar:1.1.4:compile
> [INFO] | +- org.freemarker:freemarker:jar:2.3.13:compile
> [INFO] | +- oro:oro:jar:2.0.8:compile
> [INFO] | +- org.geotools:gt-cql:jar:2.5-SNAPSHOT:compile
> [INF
[jira] Commented: (MNG-3627) Maven complains for the lack of a test dependency even when skipping tests
[
http://jira.codehaus.org/browse/MNG-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139314#action_139314
]
Andrea Aime commented on MNG-3627:
--
This makes lots of sense considering how Maven is implemented, a bit less from
the point of view of the unaware user trying to build without building tests
for the first time ;)
> Maven complains for the lack of a test dependency even when skipping tests
> --
>
> Key: MNG-3627
> URL: http://jira.codehaus.org/browse/MNG-3627
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 2.0.9
>Reporter: Andrea Aime
>
> Trying to build GeoServer trunk without tests (-Dmaven.test.skip=true) we're
> getting an error message stating that some jars marked as test dependencies
> are not found. In particular, these are the tests jar of another module in
> the build, which is not getting built because of the test.skip setting and
> it's not already available on the repository.
> Yet mvn dependency:tree does report the following:
> {panel}
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'dependency'.
> [INFO]
>
> [INFO] Building Web Coverage Service 1.1.1 Module
> [INFO]task-segment: [dependency:tree]
> [INFO]
>
> [INFO] [dependency:tree]
> [INFO] org.geoserver:wcs1_1:jar:1.8.0-SNAPSHOT
> [INFO] +- org.geoserver:main:jar:1.8.0-SNAPSHOT:compile
> [INFO] | +- org.geoserver:data:jar:1.8.0-SNAPSHOT:compile
> [INFO] | | +- org.geoserver:platform:jar:1.8.0-SNAPSHOT:compile
> [INFO] | | | +- javax.media:jai_core:jar:1.1.3:compile
> [INFO] | | | +- javax.media:jai_codec:jar:1.1.3:compile
> [INFO] | | | \- javax.media:jai_imageio:jar:1.1:compile
> [INFO] | | +- org.geotools:gt-epsg-hsql:jar:2.5-SNAPSHOT:compile
> [INFO] | | +- org.geotools:gt-h2:jar:2.5-SNAPSHOT:compile
> [INFO] | | | +- org.h2database:h2:jar:1.0-SNAPSHOT:compile
> [INFO] | | | +- org.openplans:spatialdbbox:jar:1.0-SNAPSHOT:compile
> [INFO] | | | \- mysql:mysql-connector-java:jar:5.1.5:compile
> [INFO] | | +- org.geotools:gt-property:jar:2.5-SNAPSHOT:compile
> [INFO] | | +- org.geotools.xsd:gt-xsd-gml2:jar:2.5-SNAPSHOT:compile
> [INFO] | | \- xml-apis:xml-apis-xerces:jar:2.7.1:compile
> [INFO] | +- org.geoserver:ows:jar:1.8.0-SNAPSHOT:compile
> [INFO] | | +- org.acegisecurity:acegi-security:jar:1.0.3:compile
> [INFO] | | | +- org.springframework:spring-jdbc:jar:2.5.2:compile (version
> managed from 1.2.8)
> [INFO] | | | | \- org.springframework:spring-tx:jar:2.5.2:compile
> [INFO] | | | \- commons-codec:commons-codec:jar:1.3:compile
> [INFO] | | +- commons-lang:commons-lang:jar:2.1:compile
> [INFO] | | +- org.geotools.xsd:gt-xsd-core:jar:2.5-SNAPSHOT:compile
> [INFO] | | \- xpp3:xpp3:jar:1.1.3.4.O:compile
> [INFO] | +- javax.servlet:servlet-api:jar:2.4:compile
> [INFO] | +- org.restlet:org.restlet:jar:1.0.8:compile (version managed from
> 1.0.5)
> [INFO] | +- org.restlet:org.restlet.ext.freemarker:jar:1.0.8:compile
> (version managed from 1.0.5)
> [INFO] | +-
> com.noelios.restlet:com.noelios.restlet.ext.servlet:jar:1.0.8:compile
> (version managed from 1.0.5)
> [INFO] | | \- com.noelios.restlet:com.noelios.restlet:jar:1.0.8:compile
> [INFO] | +- net.sf.json-lib:json-lib:jar:jdk13:2.1:compile
> [INFO] | | +- commons-collections:commons-collections:jar:3.1:compile
> [INFO] | | \- net.sf.ezmorph:ezmorph:jar:1.0.3:compile
> [INFO] | +- struts:struts:jar:1.2.9:compile
> [INFO] | | \- antlr:antlr:jar:2.7.2:compile
> [INFO] | +- xml-apis:xml-apis:jar:1.0.b2:compile
> [INFO] | +- xerces:xercesImpl:jar:2.6.2:compile
> [INFO] | +- xalan:xalan:jar:2.7.0:compile
> [INFO] | +- commons-beanutils:commons-beanutils:jar:1.7.0:compile
> [INFO] | +- commons-digester:commons-digester:jar:1.7:compile
> [INFO] | +- commons-fileupload:commons-fileupload:jar:1.2.1:compile
> [INFO] | +- commons-io:commons-io:jar:1.3.2:compile
> [INFO] | +- commons-httpclient:commons-httpclient:jar:2.0:compile
> [INFO] | +- commons-validator:commons-validator:jar:1.1.4:compile
> [INFO] | +- org.freemarker:freemarker:jar:2.3.13:compile
> [INFO] | +- oro:oro:jar:2.0.8:compile
> [INFO] | +- org.geotools:gt-cql:jar:2.5-SNAPSHOT:compile
> [INFO] | +- log4j:log4j:jar:1.2.14:compile
> [INFO] | +- org.geotools:gt-coverage:jar:2.5-SNAPSHOT:compile
> [INFO] | +- org.geotools:gt-validation:jar:2.5-SNAPSHOT:compile
> [INFO] | | \- org.geotools:gt-graph:jar:2.5-SNAPSHOT:compile
> [INFO] | +- org.geotools:gt-data:jar:2.5-SNAPSHOT:compile
> [INFO] | +- org.geotools:gt-jdbc:jar:2.5-SNAPSHOT:compile
> [INFO] | | \- commons-dbcp:commons-d
[jira] Created: (MNG-3628) When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository
When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository --- Key: MNG-3628 URL: http://jira.codehaus.org/browse/MNG-3628 Project: Maven 2 Issue Type: Bug Reporter: Marc Harris Attachments: maven-offline-snapshot-problem.tar When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository. This happens when attempting to depend on a snapshot version of a module downloaded from a repository. If the snapshot version of the module is built and installed locally, the problem goes away. I will attach two projects (in a tar file) that have minimal external dependencies, and the debug output of trying to build. Here are the steps to reproduce: Environment: Maven 2.0.8 Linux 2.6.18 Artifactory 1.2.5 (rev. 1154) (this has also been reproduced by a colleague on a Windows machine). Preliminary steps: 1) Modify the pom files to refer to your actual repository instead of http://localhost:8081/artifactory/jumptap-snapshots 2) Build maven-test-project1 3) Upload the pom and jar for maven-test-project1 to your repository. Steps that cause the error to happen: 1) Delete maven-test-project1 from the local repository. 2) Build maven-test-project2 without the offline flag (mvn install). This build is successful (and downloads maven-test-project1 to the local repository). 3) Build maven-test-project2 with the offline flag (mvn -o install). This build fails, unable to resolve the maven-test-project1 artifact. Steps that cause the error not to happen 1) Build maven-test-project1 locally. This build is successful. 2) Build maven-test-project2 without the offline flag (mvn install). This build is successful. 3) Build maven-test-project2 with the offline flag (mvn -o install). This build is successful. -- 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: (MASSEMBLY-237) lineEnding ignored in a child project
[ http://jira.codehaus.org/browse/MASSEMBLY-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139331#action_139331 ] Sergei Ivanov commented on MASSEMBLY-237: - We have also stumbled upon this bug and I decided to find out the root cause. I checked out the plugin sources and added extra tracing info to the plugin code. After a few test runs, I realised that the bug can be fixed with a change in a single line of code. class/method: org.apache.maven.plugin.assembly.format.FileSetFormatter#formatFileSetForAssembly patch against version 628941: @@ -57,7 +57,7 @@ -fileSet.setDirectory( set.getDirectory() ); +fileSet.setDirectory( archiveBaseDir.getPath() ); Is there a chance that it will be included in the next release? > lineEnding ignored in a child project > - > > Key: MASSEMBLY-237 > URL: http://jira.codehaus.org/browse/MASSEMBLY-237 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1 > Environment: Windows Vista >Reporter: Todor Todorov >Priority: Minor > > I have a parent project and a child project. The child project builds an > assembly composed of text files. > > bin > src/main/bin > unix > > *.sh > > > When I build the assembly from the child project , maven adds unix endings, > but when I build it from the parent project, lineEnding is being ignored. -- 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: (MASSEMBLY-237) lineEnding ignored in a child project
[
http://jira.codehaus.org/browse/MASSEMBLY-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139331#action_139331
]
sergei_ivanov edited comment on MASSEMBLY-237 at 6/23/08 11:59 AM:
---
We have also stumbled upon this bug and I decided to find out the root cause. I
checked out the plugin sources and added extra tracing info to the plugin code.
After a few test runs, I realised that the bug can be fixed with a change in a
single line of code.
class/method:
org.apache.maven.plugin.assembly.format.FileSetFormatter#formatFileSetForAssembly
patch against version 628941:
{noformat}
@@ -57,7 +57,7 @@
-fileSet.setDirectory( set.getDirectory() );
+fileSet.setDirectory( archiveBaseDir.getPath() );
{noformat}
Is there a chance that it will be included in the next release?
was (Author: sergei_ivanov):
We have also stumbled upon this bug and I decided to find out the root
cause. I checked out the plugin sources and added extra tracing info to the
plugin code. After a few test runs, I realised that the bug can be fixed with a
change in a single line of code.
class/method:
org.apache.maven.plugin.assembly.format.FileSetFormatter#formatFileSetForAssembly
patch against version 628941:
@@ -57,7 +57,7 @@
-fileSet.setDirectory( set.getDirectory() );
+fileSet.setDirectory( archiveBaseDir.getPath() );
Is there a chance that it will be included in the next release?
> lineEnding ignored in a child project
> -
>
> Key: MASSEMBLY-237
> URL: http://jira.codehaus.org/browse/MASSEMBLY-237
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-1
> Environment: Windows Vista
>Reporter: Todor Todorov
>Priority: Minor
>
> I have a parent project and a child project. The child project builds an
> assembly composed of text files.
>
> bin
> src/main/bin
> unix
>
> *.sh
>
>
> When I build the assembly from the child project , maven adds unix endings,
> but when I build it from the parent project, lineEnding is being ignored.
--
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: (MASSEMBLY-237) lineEnding ignored in a child project
[ http://jira.codehaus.org/browse/MASSEMBLY-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ivanov updated MASSEMBLY-237: Attachment: test.zip This is a test project I used to reproduce the problem. > lineEnding ignored in a child project > - > > Key: MASSEMBLY-237 > URL: http://jira.codehaus.org/browse/MASSEMBLY-237 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1 > Environment: Windows Vista >Reporter: Todor Todorov >Priority: Minor > Attachments: test.zip > > > I have a parent project and a child project. The child project builds an > assembly composed of text files. > > bin > src/main/bin > unix > > *.sh > > > When I build the assembly from the child project , maven adds unix endings, > but when I build it from the parent project, lineEnding is being ignored. -- 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: (ARCHETYPE-186) local archetype catalog not correctly updated
[ http://jira.codehaus.org/browse/ARCHETYPE-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raphaël Piéroni closed ARCHETYPE-186. - Resolution: Fixed Fix Version/s: 2.0-alpha-4 Fixed since revision 670687 > local archetype catalog not correctly updated > - > > Key: ARCHETYPE-186 > URL: http://jira.codehaus.org/browse/ARCHETYPE-186 > Project: Maven Archetype > Issue Type: Bug > Components: Plugin >Affects Versions: 2.0-alpha-3 > Environment: Windows XP, java 1.5 >Reporter: Chris Graham >Priority: Trivial > Fix For: 2.0-alpha-4 > > > The archetype:update-local-catalog step is not correctly updating the > archetype-catalog.xml file. > It is taking the element from the POM of the archetype and writing it > as the in the archetype-catalog.xml file. > Shouldn't it be using the element itself (if provided, which is > is)? > Eg, given this from the POM of the archetype: > Project Accelerator - Sample Project. > WarpSpeed archetype for creating multi module project that > has our EAR, EJB, WAR and Resource projects defined for us. > The archetype-catalog.xml file is written out as: > > au.com.warpspeed.archetypes > sample-project > 1.0-SNAPSHOT > Project Accelerator - Sample Project. > -- 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-2119) please sync groupId com.etxjs with central
please sync groupId com.etxjs with central -- Key: MAVENUPLOAD-2119 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2119 Project: Maven Upload Requests Issue Type: Wish Reporter: nicolas de loof extjs provides support and enhancements for JavaScript and GWT web applications -- 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: (ARCHETYPE-138) When create-from-project if existing variable is found escape the variable
[
http://jira.codehaus.org/browse/ARCHETYPE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raphaël Piéroni closed ARCHETYPE-138.
-
Resolution: Fixed
Fix Version/s: 2.0-alpha-4
fixed since revision 670722
> When create-from-project if existing variable is found escape the variable
> --
>
> Key: ARCHETYPE-138
> URL: http://jira.codehaus.org/browse/ARCHETYPE-138
> Project: Maven Archetype
> Issue Type: Improvement
> Components: Creator
>Affects Versions: 2.0-alpha-2
>Reporter: Mike Youngstrom
> Fix For: 2.0-alpha-4
>
>
> If i have a file in my project that has a maven filter variable such as
> ${groupId}. When I do a archetype:create-from-project on that project and
> the archetype plugin detects a conflict between it's variables and this
> variable then the archetype plugin should escape that variable "\$${groupId}"
> instead of ignoring it.
> If you don't think this would be a good general rule then perhaps it can at
> least be an option?
> 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] Closed: (ARCHETYPE-151) Add Myfaces Archetypes to archetype-catalog.xml
[ http://jira.codehaus.org/browse/ARCHETYPE-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raphaël Piéroni closed ARCHETYPE-151. - Resolution: Fixed Fix Version/s: 2.0-alpha-4 catalog updated > Add Myfaces Archetypes to archetype-catalog.xml > --- > > Key: ARCHETYPE-151 > URL: http://jira.codehaus.org/browse/ARCHETYPE-151 > Project: Maven Archetype > Issue Type: Improvement > Components: Archetypes >Affects Versions: 2.0-alpha-2 >Reporter: Leonardo Uribe > Fix For: 2.0-alpha-4 > > > It could be good if by default you can choose the following archetypes to the > default or internal archetype-catalog.xml: > It's as simple as add the nodes to the file on archetype-common > project. > > > > > org.apache.myfaces.buildtools > myfaces-archetype-helloworld > 1.0.0 > http://repo1.maven.org/maven2 > Simple Web application using Apache Myfaces > > > org.apache.myfaces.buildtools > myfaces-archetype-helloworld-facelets > 1.0.0 > http://repo1.maven.org/maven2 > A simple archetype using MyFaces and facelets > > > org.apache.myfaces.buildtools > myfaces-archetype-trinidad > 1.0 > http://repo1.maven.org/maven2 > A simple archetype using Myfaces and Trinidad > > > org.apache.myfaces.buildtools > myfaces-archetype-jsfcomponents > 1.0 > http://repo1.maven.org/maven2 > A simple archetype for create custom JSF components using > MyFaces > > > -- 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: (ARCHETYPE-152) sources in archetype.xml will not work outside of src/main/java dir.
[ http://jira.codehaus.org/browse/ARCHETYPE-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raphaël Piéroni closed ARCHETYPE-152. - Resolution: Won't Fix Obsolete as stated by Thomas > sources in archetype.xml will not work outside of src/main/java dir. > > > Key: ARCHETYPE-152 > URL: http://jira.codehaus.org/browse/ARCHETYPE-152 > Project: Maven Archetype > Issue Type: Bug > Components: Archetypes >Affects Versions: 2.0-alpha-2 > Environment: MacOSX and WindowsXP >Reporter: Zemian Deng > > If source is not in src/main/java with ".java" files, the or > elements in META-INF/archetype.xml will cause errors of "files > not found" when run. This used to work on 1.0-alpha-7. > Example of failed Testcase in the META-INF/archetype.xml file: > > src/main/scala/App.scala > > > src/test/scala/AppTest.scala > -- 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: (ARCHETYPE-70) Add project description as a mojo parameter
[
http://jira.codehaus.org/browse/ARCHETYPE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raphaël Piéroni closed ARCHETYPE-70.
Resolution: Cannot Reproduce
> Add project description as a mojo parameter
> ---
>
> Key: ARCHETYPE-70
> URL: http://jira.codehaus.org/browse/ARCHETYPE-70
> Project: Maven Archetype
> Issue Type: New Feature
> Components: Plugin
>Reporter: Michael Heuer
>Priority: Minor
> Fix For: 2.0-alpha-1
>
> Attachments: patch.txt
>
>
> For my archetype bundle, I require the project description as a parameter.
> I use it in the pom.xml
> ${description}
> in a license HEADER.txt
> /*
> ${artifactId} ${description}
> Copyright ...
> in a package.html
>
>
> ${description}
>
>
> and so on.
> The attached patch to MavenArchetypeMojo.java provides a project description
> parameter in addition to project groupId, artifactId, and version:
> $ mvn -X archetype:create
> -DgroupId=foo
> -DartifactId=bar
> -Dversion=1.0-SNAPSHOT
> -Ddescription="bar description." ...
--
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-187) update documentation example create-batch.html
update documentation example create-batch.html -- Key: ARCHETYPE-187 URL: http://jira.codehaus.org/browse/ARCHETYPE-187 Project: Maven Archetype Issue Type: Sub-task Components: Plugin Affects Versions: 2.0-alpha-3 Reporter: Raphaël Piéroni This document is outdated, and show irrelevant property -Dpackage=1.5 -- 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
