[jira] Created: (WAGON-320) A possibility to suppress FTP logs
A possibility to suppress FTP logs
--
Key: WAGON-320
URL: http://jira.codehaus.org/browse/WAGON-320
Project: Maven Wagon
Issue Type: Improvement
Components: wagon-ftp
Affects Versions: 1.0-beta-7
Reporter: Yegor Bugayenko
I can't understand how can I suppress (or control) FTP logs in Maven output
when using {{wagon-ftp}}. Now everything, including login/password, is dropped
into maven output.
Would be nice to have such a feature.
Similar question is here: http://stackoverflow.com/questions/4564018
--
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: (ARCHETYPE-355) NPE in DefaultArchetypeArtifactManager.closeZipFile when running integration-test goal
[
http://jira.codehaus.org/browse/ARCHETYPE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated ARCHETYPE-355:
Description:
After successfully creating an archetype from a project (using
archetype:create-from-project), a NullPointerException is encountered when
executing the "integration-test" goal of the archetype plugin. The steps to
reproduce are:
{noformat}cd /tmp
svn co
https://squirrel-sql.svn.sourceforge.net/svnroot/squirrel-sql/trunk/sql12/plugins/example
example
cd example
mvn -X clean install > build.log
mvn -X archetype:create-from-project > archetype-create.log
cd /tmp/example/target/generated-sources/archetype
mvn -X -e archetype:integration-test > archetype-test.log{noformat}
The NullPointerException is listed at the bottom of
/tmp/example/target/generated-sources/archetype/archetype-test.log and appears
as follows:
{noformat}Caused by: java.lang.NullPointerException
at
org.apache.maven.archetype.common.DefaultArchetypeArtifactManager.closeZipFile(DefaultArchetypeArtifactManager.java:588)
at
org.apache.maven.archetype.common.DefaultArchetypeArtifactManager.isFileSetArchetype(DefaultArchetypeArtifactManager.java:200)
at
org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:104)
at
org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:149)
at
org.apache.maven.archetype.mojos.IntegrationTestMojo.processIntegrationTest(IntegrationTestMojo.java:237)
at
org.apache.maven.archetype.mojos.IntegrationTestMojo.execute(IntegrationTestMojo.java:108)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107){noformat}
The attached zip file contains all of the logs that were generated. The source
is available on the web with the svn checkout listed above for convenience.
was:
After successfully creating an archetype from a project (using
archetype:create-from-project), a NullPointerException is encountered when
executing the "integration-test" goal of the archetype plugin. The steps to
reproduce are:
cd /tmp
svn co
https://squirrel-sql.svn.sourceforge.net/svnroot/squirrel-sql/trunk/sql12/plugins/example
example
cd example
mvn -X clean install > build.log
mvn -X archetype:create-from-project > archetype-create.log
cd /tmp/example/target/generated-sources/archetype
mvn -X -e archetype:integration-test > archetype-test.log
The NullPointerException is listed at the bottom of
/tmp/example/target/generated-sources/archetype/archetype-test.log and appears
as follows:
Caused by: java.lang.NullPointerException
at
org.apache.maven.archetype.common.DefaultArchetypeArtifactManager.closeZipFile(DefaultArchetypeArtifactManager.java:588)
at
org.apache.maven.archetype.common.DefaultArchetypeArtifactManager.isFileSetArchetype(DefaultArchetypeArtifactManager.java:200)
at
org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:104)
at
org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:149)
at
org.apache.maven.archetype.mojos.IntegrationTestMojo.processIntegrationTest(IntegrationTestMojo.java:237)
at
org.apache.maven.archetype.mojos.IntegrationTestMojo.execute(IntegrationTestMojo.java:108)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
The attached zip file contains all of the logs that were generated. The source
is available on the web with the svn checkout listed above for convenience.
> NPE in DefaultArchetypeArtifactManager.closeZipFile when running
> integration-test goal
> --
>
> Key: ARCHETYPE-355
> URL: http://jira.codehaus.org/browse/ARCHETYPE-355
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 2.0
> Environment: Apache Maven 3.0.1 (r1038046; 2010-11-23 05:58:32-0500)
> Java version: 1.6.0_14
> Java home: /opt/jdk1.6.0_14_x64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.35-24-generic" arch: "amd64" Family: "unix"
>Reporter: Rob Manning
> Attachments: logs.zip
>
>
> After successfully creating an archetype from a project (using
> archetype:create-from-project), a NullPointerException is encountered when
> executing the "integration-test" goal of the archetype plugin. The steps to
> reproduce are:
> {noformat}cd /tmp
> svn co
> https://squirrel-sql.svn.sourceforge.net/svnroot/squirrel-sql/trunk/sql12/plugins/example
> example
> cd example
> mvn -X clean install > build.log
> mvn -X ar
[jira] Commented: (MSITE-227) site:deploy -> wrong links in ${modules} when artifactId=module's directory
[
http://jira.codehaus.org/browse/MSITE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250004#action_250004
]
Lukas Theussl commented on MSITE-227:
-
I'm not following your points above. If you cannot use absolute URLs and you
cannot use relative URLs, then what would you like to use? The point is that in
general single modules can be deployed to different locations than what is
given by their relative source location. Their final relative locations are
determined by the url elements in the poms, as that's where the single sites
are supposed to end up at. This is
[documented|http://maven.apache.org/plugins/maven-site-plugin/faq.html#Use_of_url]
and that's the way it is currently supposed to work. (As a side note, I agree
that it shouldn't be like that, see MSITE-535)
> site:deploy -> wrong links in ${modules} when artifactId=module's directory
> ---
>
> Key: MSITE-227
> URL: http://jira.codehaus.org/browse/MSITE-227
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: multi module
>Affects Versions: 2.0-beta-5, 2.0
> Environment: Eclipse IDE
>Reporter: Guimiot Isabelle
>Assignee: Lukas Theussl
> Attachments: MSITE-227-working.zip, MSITE-227.zip
>
>
> I have a problem in the ${modules} part when I run the site:deploy goal.
> my project contains a root module and 2 sub-modules, at the same directory
> depth (I'm using Eclipse) :
> workspace/myRoot/
> workspace/myModule1/
> workspace/myModule2/
> my root pom contains this module declaration :
>
> ../myModule1
> ../myModule1
>
> the site:deploy goal gives this structure :
> [deploydir]/myRoot/index.html --> root's index
> [deploydir]/myRoot/myModule1/index.html --> first module's index
> [deploydir]/myRoot/myModule2/index.html --> second module's index
> when the project name (directory name in the workspace) and the artifactId
> are exactly the same, I have wrong links, both in root and in sub-modules
> pages :
> - in the root page, my links to submodules are like this :
> Modules
>
>
>myModule1
>
>
>myModule2
>
>
> - and in both modules pages, my link to the parent project is like this :
> Parent project
>
>
>myRoot
>
>
> The weirdest thing is that everything is fine when the artefactId and the
> eclipse project name (directory) are different !!! the problem appears only
> when they are identical...
> Thanks for your help !
--
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: (MPIR-215) java.lang.ArrayIndexOutOfBoundsException: 1 - Empty POM Project
[ http://jira.codehaus.org/browse/MPIR-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MPIR-215. -- Resolution: Not A Bug Assignee: Lukas Theussl Use site plugin >= 2.1 > java.lang.ArrayIndexOutOfBoundsException: 1 - Empty POM Project > --- > > Key: MPIR-215 > URL: http://jira.codehaus.org/browse/MPIR-215 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug >Affects Versions: 2.3.1 > Environment: MacBook Pro MacOSX > Maven 2.2.1 > Java 1.6.0_22 >Reporter: John Patrick >Assignee: Lukas Theussl > Attachments: error.log, pom.xml, pom.xml > > > Creating a website using an empty project results in a > ArrayIndexOutOfBoundsException. > Using the attached pom and command line below, triggers the error. > $ mvn -N clean site -- 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: (ARCHETYPE-342) display information message during project creation from a fileset archetype like it is done for old 1.x archetype
[
http://jira.codehaus.org/browse/ARCHETYPE-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated ARCHETYPE-342:
Description:
following message
{noformat}[INFO]
[INFO] Using following parameters for creating project from Old (1.x)
Archetype: maven-archetype-quickstart:1.1
[INFO]
[INFO] Parameter: groupId, Value: gr
[INFO] Parameter: packageName, Value: gr
[INFO] Parameter: basedir, Value: /home/herve/tmp
[INFO] Parameter: package, Value: gr
[INFO] Parameter: version, Value: 1.0-SNAPSHOT
[INFO] Parameter: artifactId, Value: a
[INFO] project created from Old (1.x) Archetype in dir:
/home/herve/tmp/a{noformat}
is useful: it should be displayed with fileset archetype too (actually
absolutely nothing is displayed)
was:
following message
{noformat}[INFO]
[INFO] Using following parameters for creating project from Old (1.x)
Archetype: maven-archetype-quickstart:1.1
[INFO]
[INFO] Parameter: groupId, Value: gr
[INFO] Parameter: packageName, Value: gr
[INFO] Parameter: basedir, Value: /home/herve/tmp
[INFO] Parameter: package, Value: gr
[INFO] Parameter: version, Value: 1.0-SNAPSHOT
[INFO] Parameter: artifactId, Value: a
[INFO] * End of debug info from resources from generated
POM ***
[INFO] project created from Old (1.x) Archetype in dir:
/home/herve/tmp/a{noformat}
is useful: it should be displayed with fileset archetype too (actually
absolutely nothing is displayed)
> display information message during project creation from a fileset archetype
> like it is done for old 1.x archetype
> --
>
> Key: ARCHETYPE-342
> URL: http://jira.codehaus.org/browse/ARCHETYPE-342
> Project: Maven Archetype
> Issue Type: Improvement
> Components: Generator
>Affects Versions: 2.0
>Reporter: Herve Boutemy
> Fix For: 2.1
>
>
> following message
> {noformat}[INFO]
>
> [INFO] Using following parameters for creating project from Old (1.x)
> Archetype: maven-archetype-quickstart:1.1
> [INFO]
>
> [INFO] Parameter: groupId, Value: gr
> [INFO] Parameter: packageName, Value: gr
> [INFO] Parameter: basedir, Value: /home/herve/tmp
> [INFO] Parameter: package, Value: gr
> [INFO] Parameter: version, Value: 1.0-SNAPSHOT
> [INFO] Parameter: artifactId, Value: a
> [INFO] project created from Old (1.x) Archetype in dir:
> /home/herve/tmp/a{noformat}
> is useful: it should be displayed with fileset archetype too (actually
> absolutely nothing is displayed)
--
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-357) remove debug trace displayed as info when generating a project from an old artifact
[
http://jira.codehaus.org/browse/ARCHETYPE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed ARCHETYPE-357.
---
Resolution: Fixed
Fix Version/s: 2.1
Assignee: Herve Boutemy
done in r1053963
> remove debug trace displayed as info when generating a project from an old
> artifact
> ---
>
> Key: ARCHETYPE-357
> URL: http://jira.codehaus.org/browse/ARCHETYPE-357
> Project: Maven Archetype
> Issue Type: Bug
> Components: Generator
>Affects Versions: 2.0
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
> Fix For: 2.1
>
>
> {noformat}[INFO] * End of debug info from resources from
> generated POM ***{noformat}
> should not be displayed when creating a project.
> Full actual output follows:
> {noformat}[INFO]
>
> [INFO] Using following parameters for creating project from Old (1.x)
> Archetype: maven-archetype-quickstart:1.1
> [INFO]
>
> [INFO] Parameter: groupId, Value: gr
> [INFO] Parameter: packageName, Value: gr
> [INFO] Parameter: basedir, Value: /home/herve/tmp
> [INFO] Parameter: package, Value: gr
> [INFO] Parameter: version, Value: 1.0-SNAPSHOT
> [INFO] Parameter: artifactId, Value: a
> [INFO] * End of debug info from resources from generated
> POM ***
> [INFO] project created from Old (1.x) Archetype in dir:
> /home/herve/tmp/a{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] Created: (ARCHETYPE-357) remove debug trace displayed as info when generating a project from an old artifact
remove debug trace displayed as info when generating a project from an old
artifact
---
Key: ARCHETYPE-357
URL: http://jira.codehaus.org/browse/ARCHETYPE-357
Project: Maven Archetype
Issue Type: Bug
Components: Generator
Affects Versions: 2.0
Reporter: Herve Boutemy
{noformat}[INFO] * End of debug info from resources from
generated POM ***{noformat}
should not be displayed when creating a project.
Full actual output follows:
{noformat}[INFO]
[INFO] Using following parameters for creating project from Old (1.x)
Archetype: maven-archetype-quickstart:1.1
[INFO]
[INFO] Parameter: groupId, Value: gr
[INFO] Parameter: packageName, Value: gr
[INFO] Parameter: basedir, Value: /home/herve/tmp
[INFO] Parameter: package, Value: gr
[INFO] Parameter: version, Value: 1.0-SNAPSHOT
[INFO] Parameter: artifactId, Value: a
[INFO] * End of debug info from resources from generated
POM ***
[INFO] project created from Old (1.x) Archetype in dir:
/home/herve/tmp/a{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] Updated: (MJAR-140) Performance degredation
[
http://jira.codehaus.org/browse/MJAR-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MJAR-140:
-
Affects Version/s: 2.3
> Performance degredation
>
>
> Key: MJAR-140
> URL: http://jira.codehaus.org/browse/MJAR-140
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
>Affects Versions: 2.3, 2.3.1
>Reporter: Eran Harel
>
> I migrated maven to version 3.0.1 in order to utilize the parallel build
> experimental feature.
> As a result I get the following warning:
> {code}
> [WARNING] *
> [WARNING] * Your build is requesting parallel execution, but project *
> [WARNING] * contains the following plugin(s) that are not marked as *
> [WARNING] * @threadSafe to support parallel building. *
> [WARNING] * While this /may/ work fine, please look for plugin updates*
> [WARNING] * and/or request plugins be made thread-safe. *
> [WARNING] * If reporting an issue, report it against the plugin in*
> [WARNING] * question, not against maven-core *
> [WARNING] *
> [WARNING] The following plugins are not marked @threadSafe in DataBuilder:
> [WARNING] org.apache.maven.plugins:maven-eclipse-plugin:2.8
> [WARNING] org.apache.maven.plugins:maven-jar-plugin:2.2
> [WARNING] *
> {code}
> I upgraded the maven-jar-plugin to the latest version (2.3.1), and the
> message is gone, but now the builds take much longer: minutes added!!!
> The build takes about x 1.5 longer now.
> I also compared the maven 3 parallel build time with the new jar-plugin VS a
> serial build with the old 2.2 plugin version I had. The results are that
> same, while when using the parallel build with the 2.2 plugin I see a
> significant ~30% performance boost.
--
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: (MJAR-140) Performance degredation
[
http://jira.codehaus.org/browse/MJAR-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249970#action_249970
]
Eran Harel commented on MJAR-140:
-
2.2 results:
{code}
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 2:25.773s
[INFO] Finished at: Thu Dec 30 12:24:16 IST 2010
[INFO] Final Memory: 1001M/1575M
{code}
2.3 results
{code}
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 4:30.299s
[INFO] Finished at: Thu Dec 30 15:06:08 IST 2010
[INFO] Final Memory: 1014M/1831M
[INFO]
{code}
> Performance degredation
>
>
> Key: MJAR-140
> URL: http://jira.codehaus.org/browse/MJAR-140
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
>Affects Versions: 2.3.1
>Reporter: Eran Harel
>
> I migrated maven to version 3.0.1 in order to utilize the parallel build
> experimental feature.
> As a result I get the following warning:
> {code}
> [WARNING] *
> [WARNING] * Your build is requesting parallel execution, but project *
> [WARNING] * contains the following plugin(s) that are not marked as *
> [WARNING] * @threadSafe to support parallel building. *
> [WARNING] * While this /may/ work fine, please look for plugin updates*
> [WARNING] * and/or request plugins be made thread-safe. *
> [WARNING] * If reporting an issue, report it against the plugin in*
> [WARNING] * question, not against maven-core *
> [WARNING] *
> [WARNING] The following plugins are not marked @threadSafe in DataBuilder:
> [WARNING] org.apache.maven.plugins:maven-eclipse-plugin:2.8
> [WARNING] org.apache.maven.plugins:maven-jar-plugin:2.2
> [WARNING] *
> {code}
> I upgraded the maven-jar-plugin to the latest version (2.3.1), and the
> message is gone, but now the builds take much longer: minutes added!!!
> The build takes about x 1.5 longer now.
> I also compared the maven 3 parallel build time with the new jar-plugin VS a
> serial build with the old 2.2 plugin version I had. The results are that
> same, while when using the parallel build with the 2.2 plugin I see a
> significant ~30% performance boost.
--
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: (MJAR-140) Performance degredation
[
http://jira.codehaus.org/browse/MJAR-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249966#action_249966
]
Dennis Lundberg commented on MJAR-140:
--
Can you please try with version 2.3 of the plugin to see what results you get?
> Performance degredation
>
>
> Key: MJAR-140
> URL: http://jira.codehaus.org/browse/MJAR-140
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
>Affects Versions: 2.3.1
>Reporter: Eran Harel
>
> I migrated maven to version 3.0.1 in order to utilize the parallel build
> experimental feature.
> As a result I get the following warning:
> {code}
> [WARNING] *
> [WARNING] * Your build is requesting parallel execution, but project *
> [WARNING] * contains the following plugin(s) that are not marked as *
> [WARNING] * @threadSafe to support parallel building. *
> [WARNING] * While this /may/ work fine, please look for plugin updates*
> [WARNING] * and/or request plugins be made thread-safe. *
> [WARNING] * If reporting an issue, report it against the plugin in*
> [WARNING] * question, not against maven-core *
> [WARNING] *
> [WARNING] The following plugins are not marked @threadSafe in DataBuilder:
> [WARNING] org.apache.maven.plugins:maven-eclipse-plugin:2.8
> [WARNING] org.apache.maven.plugins:maven-jar-plugin:2.2
> [WARNING] *
> {code}
> I upgraded the maven-jar-plugin to the latest version (2.3.1), and the
> message is gone, but now the builds take much longer: minutes added!!!
> The build takes about x 1.5 longer now.
> I also compared the maven 3 parallel build time with the new jar-plugin VS a
> serial build with the old 2.2 plugin version I had. The results are that
> same, while when using the parallel build with the 2.2 plugin I see a
> significant ~30% performance boost.
--
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: (MJAR-140) Performance degredation
[
http://jira.codehaus.org/browse/MJAR-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249963#action_249963
]
Eran Harel commented on MJAR-140:
-
BTW, the 2.3.1 jar-plugin version has the same effect on maven 2.2.1 if it
helps.
> Performance degredation
>
>
> Key: MJAR-140
> URL: http://jira.codehaus.org/browse/MJAR-140
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
>Affects Versions: 2.3.1
>Reporter: Eran Harel
>
> I migrated maven to version 3.0.1 in order to utilize the parallel build
> experimental feature.
> As a result I get the following warning:
> {code}
> [WARNING] *
> [WARNING] * Your build is requesting parallel execution, but project *
> [WARNING] * contains the following plugin(s) that are not marked as *
> [WARNING] * @threadSafe to support parallel building. *
> [WARNING] * While this /may/ work fine, please look for plugin updates*
> [WARNING] * and/or request plugins be made thread-safe. *
> [WARNING] * If reporting an issue, report it against the plugin in*
> [WARNING] * question, not against maven-core *
> [WARNING] *
> [WARNING] The following plugins are not marked @threadSafe in DataBuilder:
> [WARNING] org.apache.maven.plugins:maven-eclipse-plugin:2.8
> [WARNING] org.apache.maven.plugins:maven-jar-plugin:2.2
> [WARNING] *
> {code}
> I upgraded the maven-jar-plugin to the latest version (2.3.1), and the
> message is gone, but now the builds take much longer: minutes added!!!
> The build takes about x 1.5 longer now.
> I also compared the maven 3 parallel build time with the new jar-plugin VS a
> serial build with the old 2.2 plugin version I had. The results are that
> same, while when using the parallel build with the 2.2 plugin I see a
> significant ~30% performance boost.
--
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: (MJAR-140) Performance degredation
Performance degredation
Key: MJAR-140
URL: http://jira.codehaus.org/browse/MJAR-140
Project: Maven 2.x Jar Plugin
Issue Type: Bug
Affects Versions: 2.3.1
Reporter: Eran Harel
I migrated maven to version 3.0.1 in order to utilize the parallel build
experimental feature.
As a result I get the following warning:
{code}
[WARNING] *
[WARNING] * Your build is requesting parallel execution, but project *
[WARNING] * contains the following plugin(s) that are not marked as *
[WARNING] * @threadSafe to support parallel building. *
[WARNING] * While this /may/ work fine, please look for plugin updates*
[WARNING] * and/or request plugins be made thread-safe. *
[WARNING] * If reporting an issue, report it against the plugin in*
[WARNING] * question, not against maven-core *
[WARNING] *
[WARNING] The following plugins are not marked @threadSafe in DataBuilder:
[WARNING] org.apache.maven.plugins:maven-eclipse-plugin:2.8
[WARNING] org.apache.maven.plugins:maven-jar-plugin:2.2
[WARNING] *
{code}
I upgraded the maven-jar-plugin to the latest version (2.3.1), and the message
is gone, but now the builds take much longer: minutes added!!!
The build takes about x 1.5 longer now.
I also compared the maven 3 parallel build time with the new jar-plugin VS a
serial build with the old 2.2 plugin version I had. The results are that same,
while when using the parallel build with the 2.2 plugin I see a significant
~30% performance boost.
--
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: (MNGSITE-125) Maven 3.x Plugin Compatibility Matrix Selenium entry needs updating
[ http://jira.codehaus.org/browse/MNGSITE-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MNGSITE-125. Resolution: Fixed done. Thanks for reporting this. > Maven 3.x Plugin Compatibility Matrix Selenium entry needs updating > --- > > Key: MNGSITE-125 > URL: http://jira.codehaus.org/browse/MNGSITE-125 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Michael Vorburger >Assignee: Olivier Lamy >Priority: Minor > > https://cwiki.apache.org/MAVEN/maven-3x-plugin-compatibility-matrix.html > should be updated for the Selenium Maven Plugin to instead of Incompatible > say No known incompatibilities with min. version 1.1 (instead of 1.0) > following http://jira.codehaus.org/browse/MSELENIUM-66 / > http://olamy.blogspot.com/2010/10/maven-selenium-plugin-11-maven-3.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
