[jira] Closed: (WAGON-104) File handle leak in the WebDavWagon.put method
[ http://jira.codehaus.org/browse/WAGON-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-104. -- Assignee: Brett Porter Resolution: Fixed fixed during WAGON-109 File handle leak in the WebDavWagon.put method -- Key: WAGON-104 URL: http://jira.codehaus.org/browse/WAGON-104 Project: Maven Wagon Issue Type: Bug Components: wagon-webdav Affects Versions: 1.0-beta-2 Reporter: Kohsuke Kawaguchi Assignee: Brett Porter Fix For: 1.0-beta-3 PutInputStream created at line 286 is never closed. (commons-httpclient doesn't close it, either, at least as of 3.1) A finally block is needed here to properly dispose the InputStream. This affects the long-running process like Hudson, and eventually cause the file descriptor shortage. -- 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-3242) It's not possible to get a property with unescaped sign for urls
[ http://jira.codehaus.org/browse/MNG-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135465#action_135465 ] Joel Marsden commented on MNG-3242: --- It is possible to work around this issue by using amp;amp; in the property It's not possible to get a property with unescaped sign for urls -- Key: MNG-3242 URL: http://jira.codehaus.org/browse/MNG-3242 Project: Maven 2 Issue Type: Bug Components: General Affects Versions: 2.0.6 Reporter: Nils Eckert Fix For: 2.0.x Attachments: mvntest-20080327.zip I found no way to create a property with a not escaped ampersand (-sign). This is needed for a MySQL jdbc-connection String with some connection variabled and should be filtered in a properties file during compile phase. It tried to escape it with amp; This leeds to following error: Project build error Cannot read project model from interpolating filter of serialized version. It is no option to use a double escaping with amp;amp;. Here I get a amp; in my connection url. I also tried to use a [CDATA[ ... ]] with the same problems. It's not possible to use sign. And if I use amp; this escaped tag appears in my properties file after filtering. -- 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-3242) It's not possible to get a property with unescaped sign for urls
[ http://jira.codehaus.org/browse/MNG-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135466#action_135466 ] Joel Marsden commented on MNG-3242: --- My comment came out incorrect (due to the html escape!) - it is possible to work around using amp; amp; in the property (no space / quotes) It's not possible to get a property with unescaped sign for urls -- Key: MNG-3242 URL: http://jira.codehaus.org/browse/MNG-3242 Project: Maven 2 Issue Type: Bug Components: General Affects Versions: 2.0.6 Reporter: Nils Eckert Fix For: 2.0.x Attachments: mvntest-20080327.zip I found no way to create a property with a not escaped ampersand (-sign). This is needed for a MySQL jdbc-connection String with some connection variabled and should be filtered in a properties file during compile phase. It tried to escape it with amp; This leeds to following error: Project build error Cannot read project model from interpolating filter of serialized version. It is no option to use a double escaping with amp;amp;. Here I get a amp; in my connection url. I also tried to use a [CDATA[ ... ]] with the same problems. It's not possible to use sign. And if I use amp; this escaped tag appears in my properties file after filtering. -- 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-3588) ${maven.repo.local} in settings.xml doesn't work.
${maven.repo.local} in settings.xml doesn't work.
-
Key: MNG-3588
URL: http://jira.codehaus.org/browse/MNG-3588
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.9
Reporter: Marcin Kuthan
Priority: Minor
I can't use ${maven.repo.local} parameter inside settings.xml file. The
parameter is simply ignored.
settings
localRepositoryc:\base_repo_location/localRepository
profiles
profile
idmy-profile/id
properties
maven.repo.localC:\alternative_repo_location/maven.repo.local
/properties
/profile
/profiles
/settings
When I run
mvn -P my-profile package
all downloaded artifacts are stored under c:\base_repo_location not
C:\alternative_repo_location.
When I run
mvn -Dmaven.repo.local=C:\alternative_repo_location package package
artifacts are stored under C:\alternative_repo_location as I expected.
--
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: (WAGON-79) ConcurrentModificationException : TransferEventSupport needs synchronization
[ http://jira.codehaus.org/browse/WAGON-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-79. - Assignee: Brett Porter Resolution: Fixed applied the main patch - I think the thread safety test is problematic due to timing and threading, so we can just retain the primitives. I used the method level syncs from the patch since it would be equivalent to blocks that sync on listeners ConcurrentModificationException : TransferEventSupport needs synchronization Key: WAGON-79 URL: http://jira.codehaus.org/browse/WAGON-79 Project: Maven Wagon Issue Type: Bug Components: wagon-provider-api Affects Versions: 1.0-beta-3 Environment: archiva Snapshot Reporter: nicolas de loof Assignee: Brett Porter Fix For: 1.0-beta-3 Attachments: WAGON-79-testcase.patch, WAGON-79.patch I get some thraead-safety issues with maven archiva : 2007-04-02 10:11:25,392 [http--1] ERROR [RepositoryServlet]- Servlet.service() pour la servlet RepositoryServlet a généré une exception java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(Unknown Source) at java.util.AbstractList$Itr.next(Unknown Source) at org.apache.maven.wagon.events.TransferEventSupport.fireTransferProgress (TransferEventSupport.java:117) at org.apache.maven.wagon.AbstractWagon.fireTransferProgress(AbstractWagon.java:350) There is a thread-safety issue in Wagon TransferEventSupport The listeners list is an ArrayList and add/remove/fireEvent methods are not synchronized. This requires either synchronization or use of a CopyOnWriteArrayList (java5 or backport). -- 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-3242) It's not possible to get a property with unescaped sign for urls
[ http://jira.codehaus.org/browse/MNG-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135468#action_135468 ] Joel Marsden commented on MNG-3242: --- Aasssaargh - third time's a charm - to work around use this: amp;amp;amp; It's not possible to get a property with unescaped sign for urls -- Key: MNG-3242 URL: http://jira.codehaus.org/browse/MNG-3242 Project: Maven 2 Issue Type: Bug Components: General Affects Versions: 2.0.6 Reporter: Nils Eckert Fix For: 2.0.x Attachments: mvntest-20080327.zip I found no way to create a property with a not escaped ampersand (-sign). This is needed for a MySQL jdbc-connection String with some connection variabled and should be filtered in a properties file during compile phase. It tried to escape it with amp; This leeds to following error: Project build error Cannot read project model from interpolating filter of serialized version. It is no option to use a double escaping with amp;amp;. Here I get a amp; in my connection url. I also tried to use a [CDATA[ ... ]] with the same problems. It's not possible to use sign. And if I use amp; this escaped tag appears in my properties file after filtering. -- 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: (WAGON-90) The getIfNewer method fails to work if file doesn't exist locally when using repo proxy
[ http://jira.codehaus.org/browse/WAGON-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-90. - Assignee: Brett Porter Resolution: Fixed The getIfNewer method fails to work if file doesn't exist locally when using repo proxy --- Key: WAGON-90 URL: http://jira.codehaus.org/browse/WAGON-90 Project: Maven Wagon Issue Type: Bug Components: wagon-provider-api Affects Versions: 1.0-beta-2 Reporter: Dário Oliveros Assignee: Brett Porter Fix For: 1.0-beta-3 When compiling a maven project which is of maven-plugin packaging type, the maven-plugin-plugin-version.jar is not downloaded from an internal repo (archiva repo manager) at all. I've noticed that the 'resource.getLastModified()' method call returns 0 which causes the following if statement to fail since timestamp is also 0: if ( resource.getLastModified() timestamp ) By replacing '' with '=' the problem goes away, but I am not sure if it's a valid fix. BTW, this bug may be related to http://jira.codehaus.org/browse/WAGONHTTP-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
[jira] Commented: (MENFORCER-42) Maven-Enforcer-Plugin fails in multimodule project when artifacts not in repository
[
http://jira.codehaus.org/browse/MENFORCER-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135472#action_135472
]
Michael Brackx commented on MENFORCER-42:
-
I was indeed using enforce-once. Using enforce now. Thanks.
Maven-Enforcer-Plugin fails in multimodule project when artifacts not in
repository
---
Key: MENFORCER-42
URL: http://jira.codehaus.org/browse/MENFORCER-42
Project: Maven 2.x Enforcer Plugin
Issue Type: Bug
Components: Plugin
Affects Versions: 1.0-alpha-3, 1.0
Environment: Tested with Maven 2.0.7 and 2.0.8 on Linux with Java 1.5
Reporter: Martin Höller
Assignee: Brian Fox
Attachments: enforcer-test.tar.gz
Create a new simple multimodule-project and call {{mvn validate}} at the
toplevel. This leads to a build failure if none of the multimodule-artifacts
are in your local repository.
Attached is a simple test project for reproducing this bug.
--
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-3242) It's not possible to get a property with unescaped sign for urls
[
http://jira.codehaus.org/browse/MNG-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135473#action_135473
]
Nils Eckert commented on MNG-3242:
--
Yes, you are right that escaping might be a workaround.
But in my case I reference the property for some plugins and want to filter my
resources with that value.
And here is the problem. As mentioned above, using the double-escaped
{noformat}amp;{noformat}-sign the filtered properties file containts amp;
instead of the expected {noformat}{noformat}-sign.
It's not possible to get a property with unescaped sign for urls
--
Key: MNG-3242
URL: http://jira.codehaus.org/browse/MNG-3242
Project: Maven 2
Issue Type: Bug
Components: General
Affects Versions: 2.0.6
Reporter: Nils Eckert
Fix For: 2.0.x
Attachments: mvntest-20080327.zip
I found no way to create a property with a not escaped ampersand (-sign).
This is needed for a MySQL jdbc-connection String with some connection
variabled and should be filtered in a properties file during compile phase.
It tried to escape it with amp; This leeds to following error: Project build
error Cannot read project model from interpolating filter of serialized
version.
It is no option to use a double escaping with amp;amp;. Here I get a amp;
in my connection url.
I also tried to use a [CDATA[ ... ]] with the same problems. It's not
possible to use sign. And if I use amp; this escaped tag appears in my
properties file after filtering.
--
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-3242) It's not possible to get a property with unescaped sign for urls
[
http://jira.codehaus.org/browse/MNG-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135475#action_135475
]
Nils Eckert commented on MNG-3242:
--
It seems to be a little bit tricky to get these {html}{html}-signs into this
JIRA. A preview might be useful. So let's try again.
But in my case I reference the property for some plugins and want to filter my
resources with that value.
And here is the problem. As mentioned above, using the double-escaped
{html}amp;amp;{html} notation the filtered properties file containts
{html}amp;{html} instead of the expected {html}{html}-sign.
It's not possible to get a property with unescaped sign for urls
--
Key: MNG-3242
URL: http://jira.codehaus.org/browse/MNG-3242
Project: Maven 2
Issue Type: Bug
Components: General
Affects Versions: 2.0.6
Reporter: Nils Eckert
Fix For: 2.0.x
Attachments: mvntest-20080327.zip
I found no way to create a property with a not escaped ampersand (-sign).
This is needed for a MySQL jdbc-connection String with some connection
variabled and should be filtered in a properties file during compile phase.
It tried to escape it with amp; This leeds to following error: Project build
error Cannot read project model from interpolating filter of serialized
version.
It is no option to use a double escaping with amp;amp;. Here I get a amp;
in my connection url.
I also tried to use a [CDATA[ ... ]] with the same problems. It's not
possible to use sign. And if I use amp; this escaped tag appears in my
properties file after filtering.
--
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-3242) It's not possible to get a property with unescaped sign for urls
[
http://jira.codehaus.org/browse/MNG-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135476#action_135476
]
Nils Eckert commented on MNG-3242:
--
It seems to be a little bit tricky to get these {{}}-signs into this JIRA.
Third try :-)
But in my case I reference the property for some plugins and want to filter my
resources with that value.
And here is the problem. As mentioned above, using the double-escaped
{{amp;amp;}} notation the filtered properties file containts {html}amp;{html}
instead of the expected {{}}-sign.
Comment: Using }} might help.
It's not possible to get a property with unescaped sign for urls
--
Key: MNG-3242
URL: http://jira.codehaus.org/browse/MNG-3242
Project: Maven 2
Issue Type: Bug
Components: General
Affects Versions: 2.0.6
Reporter: Nils Eckert
Fix For: 2.0.x
Attachments: mvntest-20080327.zip
I found no way to create a property with a not escaped ampersand (-sign).
This is needed for a MySQL jdbc-connection String with some connection
variabled and should be filtered in a properties file during compile phase.
It tried to escape it with amp; This leeds to following error: Project build
error Cannot read project model from interpolating filter of serialized
version.
It is no option to use a double escaping with amp;amp;. Here I get a amp;
in my connection url.
I also tried to use a [CDATA[ ... ]] with the same problems. It's not
possible to use sign. And if I use amp; this escaped tag appears in my
properties file after filtering.
--
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: (WAGON-83) mvn deploy causes NPE in ChecksumObserver.transferStarted
[ http://jira.codehaus.org/browse/WAGON-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-83. - Assignee: Brett Porter Resolution: Fixed I was able to reproduce this by removing the .sha1 on beta-2, and in the latest code it no longer occurs mvn deploy causes NPE in ChecksumObserver.transferStarted -- Key: WAGON-83 URL: http://jira.codehaus.org/browse/WAGON-83 Project: Maven Wagon Issue Type: Bug Components: wagon-webdav Affects Versions: 1.0-beta-2 Reporter: Eric Barroca Assignee: Brett Porter Fix For: 1.0-beta-3 Attachments: mvn-deploy-wagon-error.log When doing a mvn deploy to an archiva repository, I get a NPE in ChecksumObserver.transferStarted. I can reproduce it every time on this project. The strange thing is that I never get it on other projects. Full debug log attached. -- 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: (WAGON-102) User Rights on Webdav : filePermissions are ignored
[ http://jira.codehaus.org/browse/WAGON-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-102. -- Assignee: Brett Porter Resolution: Won't Fix Fix Version/s: (was: 1.0-beta-3) I don't believe this is possible using HTTP or WebDAV. You probably need to configure your webdav server to store files on the file system with appropriate permissions User Rights on Webdav : filePermissions are ignored --- Key: WAGON-102 URL: http://jira.codehaus.org/browse/WAGON-102 Project: Maven Wagon Issue Type: Bug Components: wagon-webdav Environment: Linux Reporter: Alexandre Navarro Assignee: Brett Porter I configure my webdav in my settings.xmll like that server idsnapshots/id usernamerepodeployer/username passwordrepodeployer/password filePermissions444/filePermissions /server I can deploy but the user right are ignored. It is problematic for non-snapshot because you can redeploy a released jar. -- 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: (WAGON-103) Wagon Webdav does not handle HTTP redirects gracefully.
[ http://jira.codehaus.org/browse/WAGON-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-103. -- Assignee: Brett Porter Resolution: Fixed fixed through WAGON-109 Wagon Webdav does not handle HTTP redirects gracefully. --- Key: WAGON-103 URL: http://jira.codehaus.org/browse/WAGON-103 Project: Maven Wagon Issue Type: Bug Components: wagon-webdav Affects Versions: 1.0-beta-2 Reporter: James William Dumay Assignee: Brett Porter Fix For: 1.0-beta-3 Attachments: deploy.log The Wagon Dav component will not handle redirects as followRedirects is disabled in the CorrectedWebdavResource Build log is attached. -- 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-3242) It's not possible to get a property with unescaped sign for urls
[ http://jira.codehaus.org/browse/MNG-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135487#action_135487 ] Benjamin Bentmann commented on MNG-3242: bq. A preview might be useful. You might want to try out the little preview icon/button right next to the text box when creating your comment. It's not possible to get a property with unescaped sign for urls -- Key: MNG-3242 URL: http://jira.codehaus.org/browse/MNG-3242 Project: Maven 2 Issue Type: Bug Components: General Affects Versions: 2.0.6 Reporter: Nils Eckert Fix For: 2.0.x Attachments: mvntest-20080327.zip I found no way to create a property with a not escaped ampersand (-sign). This is needed for a MySQL jdbc-connection String with some connection variabled and should be filtered in a properties file during compile phase. It tried to escape it with amp; This leeds to following error: Project build error Cannot read project model from interpolating filter of serialized version. It is no option to use a double escaping with amp;amp;. Here I get a amp; in my connection url. I also tried to use a [CDATA[ ... ]] with the same problems. It's not possible to use sign. And if I use amp; this escaped tag appears in my properties file after filtering. -- 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: (WAGON-70) Deploying using scp:// hangs when proxy configured in settings.xml
[ http://jira.codehaus.org/browse/WAGON-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135488#action_135488 ] Brett Porter commented on WAGON-70: --- active is irrelevant due to a bug: see http://jira.codehaus.org/browse/MNG-2387 I'm unable to reproduce this as I just get a connection failure from the given HTTP proxy - but I suspect the above bug is the problem. You expect it to actually be disabled and it's not. Unscheduling for now. Deploying using scp:// hangs when proxy configured in settings.xml -- Key: WAGON-70 URL: http://jira.codehaus.org/browse/WAGON-70 Project: Maven Wagon Issue Type: Bug Components: wagon-ssh Affects Versions: 1.0-beta-2 Environment: Windows XP in a corporate environment that is proxied and firewalled to everywhere Reporter: Stephen Coy Fix For: 1.x For some reason, wagon-ssh is attempting to connect to the proxy defined in settings.xml (irrespective of whether it is enabled or not) in order to perform an scp transfer. This causes goals such as site:deploy to hang for some time before proceeding normally. A thread dump taken during the hang: [INFO] [site:deploy] Full thread dump Java HotSpot(TM) Client VM (1.4.2_13-b06 mixed mode): Signal Dispatcher daemon prio=10 tid=0x009cf600 nid=0xa7c waiting on condition [0x..0x] Finalizer daemon prio=9 tid=0x009ccbb8 nid=0xb84 in Object.wait() [0x02b6f000..0x02b6fd68] at java.lang.Object.wait(Native Method) - waiting on 0x104fb160 (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111) - locked 0x104fb160 (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159) Reference Handler daemon prio=10 tid=0x009cb830 nid=0xf38 in Object.wait() [0x02b2f000..0x02b2fd68] at java.lang.Object.wait(Native Method) - waiting on 0x104fb1c8 (a java.lang.ref.Reference$Lock) at java.lang.Object.wait(Object.java:429) at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:115) - locked 0x104fb1c8 (a java.lang.ref.Reference$Lock) main prio=5 tid=0x00035b28 nid=0xe90 runnable [0x0007f000..0x0007fc38] at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.net.SocketInputStream.read(SocketInputStream.java:182) at com.jcraft.jsch.ProxyHTTP.connect(Unknown Source) at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(AbstractSshWagon.java:181) at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:149) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) 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:256) 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) -- 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: (WAGON-70) Deploying using scp:// hangs when proxy configured in settings.xml
[ http://jira.codehaus.org/browse/WAGON-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated WAGON-70: -- Fix Version/s: (was: 1.0-beta-3) 1.x Deploying using scp:// hangs when proxy configured in settings.xml -- Key: WAGON-70 URL: http://jira.codehaus.org/browse/WAGON-70 Project: Maven Wagon Issue Type: Bug Components: wagon-ssh Affects Versions: 1.0-beta-2 Environment: Windows XP in a corporate environment that is proxied and firewalled to everywhere Reporter: Stephen Coy Fix For: 1.x For some reason, wagon-ssh is attempting to connect to the proxy defined in settings.xml (irrespective of whether it is enabled or not) in order to perform an scp transfer. This causes goals such as site:deploy to hang for some time before proceeding normally. A thread dump taken during the hang: [INFO] [site:deploy] Full thread dump Java HotSpot(TM) Client VM (1.4.2_13-b06 mixed mode): Signal Dispatcher daemon prio=10 tid=0x009cf600 nid=0xa7c waiting on condition [0x..0x] Finalizer daemon prio=9 tid=0x009ccbb8 nid=0xb84 in Object.wait() [0x02b6f000..0x02b6fd68] at java.lang.Object.wait(Native Method) - waiting on 0x104fb160 (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111) - locked 0x104fb160 (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159) Reference Handler daemon prio=10 tid=0x009cb830 nid=0xf38 in Object.wait() [0x02b2f000..0x02b2fd68] at java.lang.Object.wait(Native Method) - waiting on 0x104fb1c8 (a java.lang.ref.Reference$Lock) at java.lang.Object.wait(Object.java:429) at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:115) - locked 0x104fb1c8 (a java.lang.ref.Reference$Lock) main prio=5 tid=0x00035b28 nid=0xe90 runnable [0x0007f000..0x0007fc38] at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.net.SocketInputStream.read(SocketInputStream.java:182) at com.jcraft.jsch.ProxyHTTP.connect(Unknown Source) at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(AbstractSshWagon.java:181) at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:149) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) 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:256) 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) -- 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: (WAGON-209) Extend Wagon API to support the Stage Plugin
Extend Wagon API to support the Stage Plugin
Key: WAGON-209
URL: http://jira.codehaus.org/browse/WAGON-209
Project: Maven Wagon
Issue Type: New Feature
Components: wagon-provider-api
Affects Versions: 1.0-beta-2
Reporter: Benjamin Bentmann
From the source of the [Maven Stage
Plugin|http://maven.apache.org/plugins/maven-stage-plugin/]:
{code:java}
( (ScpWagon) targetWagon ).executeCommand( command );
{code}
This smells: The plugin is downcasting to an implementation class, happily
breaking the interface design and making the target wagon non-interchangeable.
The atomic Wagon operations required by the plugin should be identified and
added to the Wagon API. Wagons that can't support these new operations could
simply implement the methods by throwing an {{UnsupportedOperationException}}
exception.
--
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: (WAGON-173) Support HTTP nonProxyHost
[ http://jira.codehaus.org/browse/WAGON-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated WAGON-173: --- Issue Type: Bug (was: Sub-task) Parent: (was: WAGON-172) Support HTTP nonProxyHost - Key: WAGON-173 URL: http://jira.codehaus.org/browse/WAGON-173 Project: Maven Wagon Issue Type: Bug Components: wagon-ssh Environment: all Reporter: Denis Cabasson Fix For: 1.0-beta-3 Attachments: wagon-provider-api-patch.txt, wagon-shh-patch.txt Proxy host are supported for SSH connection, but the nonProxyHost List isn't taken into account. -- 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: (WAGON-209) Extend Wagon API to support the Stage Plugin
[
http://jira.codehaus.org/browse/WAGON-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated WAGON-209:
---
Fix Version/s: 1.0-beta-3
Extend Wagon API to support the Stage Plugin
Key: WAGON-209
URL: http://jira.codehaus.org/browse/WAGON-209
Project: Maven Wagon
Issue Type: New Feature
Components: wagon-provider-api
Affects Versions: 1.0-beta-2
Reporter: Benjamin Bentmann
Fix For: 1.0-beta-3
From the source of the [Maven Stage
Plugin|http://maven.apache.org/plugins/maven-stage-plugin/]:
{code:java}
( (ScpWagon) targetWagon ).executeCommand( command );
{code}
This smells: The plugin is downcasting to an implementation class, happily
breaking the interface design and making the target wagon non-interchangeable.
The atomic Wagon operations required by the plugin should be identified and
added to the Wagon API. Wagons that can't support these new operations could
simply implement the methods by throwing an {{UnsupportedOperationException}}
exception.
--
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: (WAGON-80) Attempt to use proxySettings even when nonProxyHosts is defined
[ http://jira.codehaus.org/browse/WAGON-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-80. - Assignee: Brett Porter Resolution: Fixed applied, great patch - thanks Attempt to use proxySettings even when nonProxyHosts is defined --- Key: WAGON-80 URL: http://jira.codehaus.org/browse/WAGON-80 Project: Maven Wagon Issue Type: Bug Components: wagon-file, wagon-ftp, wagon-http, wagon-provider-api, wagon-provider-test, wagon-scm, wagon-ssh, wagon-ssh-external, wagon-webdav Environment: Maven 2.0.5 or maven 2.0.6, this report is based on 2.0.6 Reporter: David J. M. Karlsen Assignee: Brett Porter Fix For: 1.0-beta-3 Attachments: WAGON-80-wagon-provider-api.patch site-deploy hangs because of proxy-settings: [INFO] Generate Project Team report. [DEBUG] Generating /tmp/mobilebank/mobilebank-ear/target/site/project-info.html [DEBUG] Generating /tmp/mobilebank/mobilebank-ear/target/site/project-reports.html [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-site-plugin:2.0-beta-5:deploy' -- [DEBUG] (f) inputDirectory = /tmp/mobilebank/mobilebank-ear/target/site [DEBUG] (f) project = [EMAIL PROTECTED] [DEBUG] (f) settings = [EMAIL PROTECTED] [DEBUG] -- end configuration -- [INFO] [site:deploy] If I remove the proxies/proxy element[s] from my settings.xml it works. Scp is used for deployment. mvn -X site-deply|grep -i wagon gives: [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-ssh-external:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime (selected for runtime) -- 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: (WAGON-112) Clarify value of basedir property for Repository
[
http://jira.codehaus.org/browse/WAGON-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed WAGON-112.
--
Assignee: Brett Porter
Resolution: Fixed
Clarify value of basedir property for Repository
Key: WAGON-112
URL: http://jira.codehaus.org/browse/WAGON-112
Project: Maven Wagon
Issue Type: Task
Components: wagon-provider-api
Affects Versions: 1.0-beta-2
Reporter: Benjamin Bentmann
Assignee: Brett Porter
Fix For: 1.0-beta-3
There seems to be some confusion what exactly the return value from
{{Repository.getBasedir()}} delivers:
# always some part of a URL (i.e. a string that is subject to URL-encoding) or
# something depending on the URL protocol (e.g. a normal file system path in
case of {{file://}})
The javadoc should be be extended to clearly express what contents callers of
the method have to expect such that they can handle it properly.
--
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: (WAGON-130) FTP Deploy Error: StringIndexOutOfBoundsException
[ http://jira.codehaus.org/browse/WAGON-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated WAGON-130: --- Fix Version/s: (was: 1.0-beta-3) 1.x I don't see any related fixes in commons-net - have you overcome the issue? FTP Deploy Error: StringIndexOutOfBoundsException - Key: WAGON-130 URL: http://jira.codehaus.org/browse/WAGON-130 Project: Maven Wagon Issue Type: Bug Components: wagon-ftp Environment: Client: Windows XP SP2 FTP Server: Windows XP SP2 - Filezilla (sourceforge) FTP Server is behind a Firewall/Router (NAT) Reporter: Alan Gross Fix For: 1.x FTP Connection/GET/PUT works fine with FTP Clients (Filezilla, Windows Commandline FTP Client). When calling mvn deploy the following StringIndexOutOfBoundsException occurs (see down below). Is this a known issue? FTP seems to me the easiest solution for distributionmgmt in a window environment. I was trying to deploy with SSH, but there it seems to be necessary to create a windows user account for each user deploying to the maven repository. Further it seems like User/Password Authentication is not working (only Certificates). Until now i didn't get it to work. With FTP it is possible to use one user account for all developers. Any help is appreciated!! Best regards Alan Trace (mvn deploy -e): [INFO] Retrieving previous build number from alan-maven-repo-ftp [INFO] [ERROR] FATAL ERROR [INFO] [INFO] String index out of range: -27 [INFO] [INFO] Trace java.lang.StringIndexOutOfBoundsException: String index out of range: -27 at java.lang.String.substring(String.java:1768) at org.apache.commons.net.ftp.FTPClient.__parsePassiveModeReply(FTPClien t.java:341) at org.apache.commons.net.ftp.FTPClient._openDataConnection_(FTPClient.j ava:511) at org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.ja va:2390) at org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.ja va:2364) at org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2141) at org.apache.maven.wagon.providers.ftp.FtpWagon.fillInputData(FtpWagon. java:317) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:68) at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(D efaultWagonManager.java:462) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMeta data(DefaultWagonManager.java:363) at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetada taManager.resolveAlways(DefaultRepositoryMetadataManager.java:364) at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetada taManager.resolveAlways(DefaultRepositoryMetadataManager.java:318) at org.apache.maven.artifact.transform.SnapshotTransformation.resolveLat estSnapshotBuildNumber(SnapshotTransformation.java:161) at org.apache.maven.artifact.transform.SnapshotTransformation.transformF orDeployment(SnapshotTransformation.java:100) at org.apache.maven.artifact.transform.DefaultArtifactTransformationMana ger.transformForDeployment(DefaultArtifactTransformationManager.java:78) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Def aultArtifactDeployer.java:71) at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:162 ) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
[jira] Closed: (WAGON-140) WAGONFTP Nullpointer Exception
[ http://jira.codehaus.org/browse/WAGON-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-140. -- Assignee: Brett Porter Resolution: Cannot Reproduce Fix Version/s: (was: 1.0-beta-3) this appears to be on the older 1.0-beta-1. It seems to work ok for me now. WAGONFTP Nullpointer Exception -- Key: WAGON-140 URL: http://jira.codehaus.org/browse/WAGON-140 Project: Maven Wagon Issue Type: Bug Components: wagon-ftp Environment: Solaris Reporter: Jamish Patel Assignee: Brett Porter Getting the following error similar to this user: http://jira.codehaus.org/browse/WAGONFTP-17 Pretty sure user id and password is correct for the machine that I am trying to ftp to One thing I did not understand in the url above was 'will be thrown if there is a host mismatch' Mismatch with what? Here's the exception: [INFO] Retrieving previous build number from internal-snapshot [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.wagon.providers.ftp.FtpWagon.openConnection(FtpWagon.java:127) at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:354) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:295) at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolveAlways(DefaultRepositoryMetadataManager.java:356) at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolveAlways(DefaultRepositoryMetadataManager.java:310) at org.apache.maven.artifact.transform.SnapshotTransformation.resolveLatestSnapshotBuildNumber(SnapshotTransformation.java:158) at org.apache.maven.artifact.transform.SnapshotTransformation.transformForDeployment(SnapshotTransformation.java:97) at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.transformForDeployment(DefaultArtifactTransformationManager.java:61) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:68) at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:162) -- 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: (WAGON-108) HttpException deploying to webdav
[ http://jira.codehaus.org/browse/WAGON-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-108. -- Assignee: Brett Porter Resolution: Fixed I believe the upgrade to httpclient 3.1 has taken care of that HttpException deploying to webdav - Key: WAGON-108 URL: http://jira.codehaus.org/browse/WAGON-108 Project: Maven Wagon Issue Type: Bug Components: wagon-webdav Affects Versions: 1.0-beta-2 Environment: Maven version: 2.0.9 Java version: 1.5.0_12 OS name: linux version: 2.6.22 arch: i386 Family: unix Reporter: Steffen Werner Assignee: Brett Porter Fix For: 1.0-beta-3 When trying to deploy to our webdav maven-repository the following exception occurs: [...] [INFO] [install:install] [INFO] Installing /home/sw/my-project/target/my-project.jar to /opt/maven/repository/my-project/1.0-SNAPSHOT/my-project-1.0-SNAPSHOT.jar [INFO] [deploy:deploy] altDeploymentRepository = null [INFO] Retrieving previous build number from maven-host Uploading: http://maven-host/maven/my-project/1.0-SNAPSHOT/my-project-1.0-20080416.104050-26.jar org.apache.commons.httpclient.HttpException: Unbuffered entity enclosing request can not be repeated. at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:436) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2316) at org.apache.commons.httpclient.HttpMethodBase.processRequest(HttpMethodBase.java:2651) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1087) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:643) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:497) at org.apache.maven.wagon.providers.webdav.CorrectedWebdavResource.putMethod(CorrectedWebdavResource.java:156) at org.apache.maven.wagon.providers.webdav.WebDavWagon.put(WebDavWagon.java:287) at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:244) at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:160) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:80) at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:162) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) 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:585) 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) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: PUT request for: my-project/1.0-SNAPSHOT/my-project-1.0-20080416.104050-26.jar to my-project.jar failed Unbuffered entity enclosing request can not be repeated. [...] The access.log of our maven-repository show the following: [...] maven-host - [16/Apr/2008:12:44:00 +0200] MKCOL /maven/my-project/1.0-SNAPSHOT/ HTTP/1.1 401 401 - Jakarta Commons-HttpClient/2.0.2 - - - - - - 112 maven-host devbuild [16/Apr/2008:12:44:00 +0200] MKCOL /maven/my-project/1.0-SNAPSHOT/ HTTP/1.1 405 236 - Jakarta Commons-HttpClient/2.0.2 - - - - -
[jira] Closed: (WAGON-84) exception deploying with webdav
[ http://jira.codehaus.org/browse/WAGON-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-84. - Assignee: Brett Porter Resolution: Fixed this was resolved by the switch to jackrabbit exception deploying with webdav --- Key: WAGON-84 URL: http://jira.codehaus.org/browse/WAGON-84 Project: Maven Wagon Issue Type: Bug Components: wagon-webdav Affects Versions: 1.0-beta-3 Reporter: Brian Fox Assignee: Brett Porter Fix For: 1.0-beta-3 1.0-beta-2 was working reasonably well but when I try the 1.0-RC1, it seems there is a regression: Uploading: http://sv1.tus.stchome.com/maven-repos/stc/com/stchome/adf/view/faces/adf-faces/1.0/adf-faces-1.0.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Destination path exists and is not a WebDAV collection (directory): http://sv1.tus.stchome.com/mave n-repos/stc/com/stchome/adf/view/faces/adf-faces/1.0/ [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact: Destination path exists and is not a WebDAV collec tion (directory): http://sv1.tus.stchome.com/maven-repos/stc/com/stchome/adf/view/faces/adf-faces/1.0/ at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) 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:597) 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: Error deploying artifact: Destination path exists and is not a WebDAV col lection (directory): http://sv1.tus.stchome.com/maven-repos/stc/com/stchome/adf/view/faces/adf-faces/1.0/ at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:174) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 16 more Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error deploying artifact: Destination path exists and is not a WebDAV collection (directory): http://sv1.tus.stchome.com/maven-repos/stc/com/stchome/adf/view/faces/adf-faces/1.0/ at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:94) at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:152) ... 18 more Caused by: org.apache.maven.wagon.TransferFailedException: Destination path exists and is not a WebDAV collection (directory): http: //sv1.tus.stchome.com/maven-repos/stc/com/stchome/adf/view/faces/adf-faces/1.0/ at org.apache.maven.wagon.providers.webdav.WebDavWagon.mkdirs(WebDavWagon.java:333) at org.apache.maven.wagon.providers.webdav.WebDavWagon.put(WebDavWagon.java:236) at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:237) at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:153) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:80) ... 19 more [INFO]
[jira] Updated: (MJAVADOC-126) Add the ability to load the stylesheet from a jar (resource)
[ http://jira.codehaus.org/browse/MJAVADOC-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Fernandes updated MJAVADOC-126: Attachment: 20080520-maven-javadoc-plugin-external-resources-integration-tests.zip 20080520-maven-javadoc-plugin-external-resources.patch Add the ability to load the stylesheet from a jar (resource) Key: MJAVADOC-126 URL: http://jira.codehaus.org/browse/MJAVADOC-126 Project: Maven 2.x Javadoc Plugin Issue Type: Wish Affects Versions: 2.2 Reporter: Julien S Priority: Minor Attachments: 20080520-maven-javadoc-plugin-external-resources-integration-tests.zip, 20080520-maven-javadoc-plugin-external-resources.patch Currently, the stylesheetfile has to be given as a path on the filesystem, which makes sharing quite difficult. It would be nice to be able to retrieve it from a jar (like the checkstyle and the pmd plugins). -- 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: (WAGON-173) Support HTTP nonProxyHost
[ http://jira.codehaus.org/browse/WAGON-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-173. -- Assignee: Brett Porter Resolution: Duplicate Fix Version/s: (was: 1.0-beta-3) I believe the WAGON-80 patch is a more complete solution to this Support HTTP nonProxyHost - Key: WAGON-173 URL: http://jira.codehaus.org/browse/WAGON-173 Project: Maven Wagon Issue Type: Bug Components: wagon-ssh Environment: all Reporter: Denis Cabasson Assignee: Brett Porter Attachments: wagon-provider-api-patch.txt, wagon-shh-patch.txt Proxy host are supported for SSH connection, but the nonProxyHost List isn't taken into account. -- 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: (WAGON-95) Upload fail with exception Entity closing requests cannot be redirected...
[ http://jira.codehaus.org/browse/WAGON-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-95. - Assignee: Brett Porter Resolution: Duplicate Fix Version/s: (was: 1.0-beta-3) Upload fail with exception Entity closing requests cannot be redirected... Key: WAGON-95 URL: http://jira.codehaus.org/browse/WAGON-95 Project: Maven Wagon Issue Type: Bug Components: wagon-webdav Affects Versions: 1.0-beta-3 Environment: Mac OS X, server: Archiva 1.0, wagon webdav: latest suversion version (1.0-rc1-snapshot) Reporter: Ludovic Maître Assignee: Brett Porter Priority: Minor Attachments: webdav_resource_put_nofollowredirects.txt When i try to upload a file with te webdav wagon to archiva it fail with the following exception: [INFO] Retrieving previous build number from ubik-central Uploading: http://forge.ubik-products.com/archiva/repository/ubik-central//com/ubikproducts/xsystem/xsystem/1.0-SNAPSHOT/xsystem-1.0-20071230.114939-2.pom [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Entity enclosing requests cannot be redirected without user intervention [INFO] [INFO] Trace java.lang.IllegalArgumentException: Entity enclosing requests cannot be redirected without user intervention at org.apache.commons.httpclient.methods.EntityEnclosingMethod.setFollowRedirects(EntityEnclosingMethod.java:225) at org.apache.maven.wagon.providers.webdav.CorrectedWebdavResource.putMethod(CorrectedWebdavResource.java:150) at org.apache.maven.wagon.providers.webdav.WebDavWagon.put(WebDavWagon.java:242) at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:237) at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:153) I have to put the followRedirect parameter to false for the file to be uploaed correctly: method.setFollowRedirects( super.followRedirects ); to //is it possible to follow redirects on PUT operations ? method.setFollowRedirects( false ); But i' wondering why such error happen in the first place, i guess others should have encountered it before. -- 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: (WAGON-81) connect( x , y ) deprecation cause IllegalStateExceptions
[ http://jira.codehaus.org/browse/WAGON-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-81. - Assignee: Brett Porter Resolution: Won't Fix Fix Version/s: (was: 1.0-beta-3) we rolled back the 2.0 changes connect( x , y ) deprecation cause IllegalStateExceptions - Key: WAGON-81 URL: http://jira.codehaus.org/browse/WAGON-81 Project: Maven Wagon Issue Type: Improvement Components: wagon-provider-api Affects Versions: 1.0-beta-3 Reporter: nicolas de loof Assignee: Brett Porter Priority: Trivial Attachments: abstractWagon.patch Wagon-provider-api 2.0 SNAPSHOT deprecates the connect methods with arguments (repository, proxyInfo...) Deprecation breaks existing code, as the parameters are not used to set the internal repository/proxyInfo/authenticationInfo and connect() throws an IllegalStateException Having those deprecated connect( x ) call the required setters solves the 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: (MJAVADOC-189) Allow skipping of javadoc generation
Allow skipping of javadoc generation Key: MJAVADOC-189 URL: http://jira.codehaus.org/browse/MJAVADOC-189 Project: Maven 2.x Javadoc Plugin Issue Type: Improvement Reporter: Francois Fernandes Priority: Minor Attachments: 20080520-maven-javadoc-plugin-skip-javadoc.patch As javadoc may be running a long time it would be nice to have to possibility to skip the javadoc generation, much the same like skipping surefire tests. I've attached a patch which will skip javadoc:jar if maven.javadoc.skip has been specified. -- 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: (MJAVADOC-126) Add the ability to load the stylesheet from a jar (resource)
[ http://jira.codehaus.org/browse/MJAVADOC-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135496#action_135496 ] Francois Fernandes commented on MJAVADOC-126: - I have the same problem. Attached to this Issue you'll find two files: * [^20080520-maven-javadoc-plugin-external-resources.patch]: this contains the logic for using resources artifacts which should be extracted into the javadoc target directory. * [^20080520-maven-javadoc-plugin-external-resources-integration-tests.zip]: associated integration tests Add the ability to load the stylesheet from a jar (resource) Key: MJAVADOC-126 URL: http://jira.codehaus.org/browse/MJAVADOC-126 Project: Maven 2.x Javadoc Plugin Issue Type: Wish Affects Versions: 2.2 Reporter: Julien S Priority: Minor Attachments: 20080520-maven-javadoc-plugin-external-resources-integration-tests.zip, 20080520-maven-javadoc-plugin-external-resources.patch Currently, the stylesheetfile has to be given as a path on the filesystem, which makes sharing quite difficult. It would be nice to be able to retrieve it from a jar (like the checkstyle and the pmd plugins). -- 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: (WAGON-161) wagon-ssh-common-test build is broken
[ http://jira.codehaus.org/browse/WAGON-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-161. -- Assignee: Brett Porter Resolution: Cannot Reproduce Fix Version/s: (was: 1.0-beta-3) wagon-ssh-common-test build is broken - Key: WAGON-161 URL: http://jira.codehaus.org/browse/WAGON-161 Project: Maven Wagon Issue Type: Bug Components: wagon-ssh Environment: Feisty Fawn Ubuntu Linux 2.6.20-15-generic #2 SMP i686 GNU/Linux Maven version: 2.0.6 java version 1.6.0 Java(TM) SE Runtime Environment (build 1.6.0-b105) Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode) svn: URL: http://svn.apache.org/repos/asf/maven/wagon/trunk Repository Root: http://svn.apache.org/repos/asf Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 Revision: 534973 Node Kind: directory Schedule: normal Last Changed Author: carlos Last Changed Rev: 533896 Last Changed Date: 2007-04-30 18:51:25 -0600 (Mon, 30 Apr 2007) Reporter: Tyler Peterson Assignee: Brett Porter Attachments: comment-out-test-scope.patch Trunk check-out of wagon fails compilation in wagon-ssh-common-test with several cannot find symbol errors. FWIW, the attached patch to trunk causes the build to succeed. Steps to reproduce. 1. Check out head (r533896) on trunk (http://svn.apache.org/repos/asf/maven/wagon/trunk) 2. mvn compile Expected error: Compile will fail in wagon-ssh-common-test with severl errors like the following: .../wagon/wagon-providers/wagon-ssh-common-test/src/main/java/org/apache/maven/wagon/providers/ssh/knownhost/KnownHostsProviderTestCase.java:[22,29] cannot find symbol symbol : class Wagon location: package org.apache.maven.wagon -- 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-3242) It's not possible to get a property with unescaped sign for urls
[ http://jira.codehaus.org/browse/MNG-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135501#action_135501 ] Joel Marsden commented on MNG-3242: --- Sorry Nils, you are correct. The double escape amp;amp;amp; trick works fine if you are referencing the property elsewhere in a pom but does not work through resource filtering. It's not possible to get a property with unescaped sign for urls -- Key: MNG-3242 URL: http://jira.codehaus.org/browse/MNG-3242 Project: Maven 2 Issue Type: Bug Components: General Affects Versions: 2.0.6 Reporter: Nils Eckert Fix For: 2.0.x Attachments: mvntest-20080327.zip I found no way to create a property with a not escaped ampersand (-sign). This is needed for a MySQL jdbc-connection String with some connection variabled and should be filtered in a properties file during compile phase. It tried to escape it with amp; This leeds to following error: Project build error Cannot read project model from interpolating filter of serialized version. It is no option to use a double escaping with amp;amp;. Here I get a amp; in my connection url. I also tried to use a [CDATA[ ... ]] with the same problems. It's not possible to use sign. And if I use amp; this escaped tag appears in my properties file after filtering. -- 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-2067) JasperReports 3.0.0 upload
JasperReports 3.0.0 upload -- Key: MAVENUPLOAD-2067 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2067 Project: maven-upload-requests Issue Type: Task Reporter: Teodor Danciu http://jasperreports.sf.net/maven/jasperreports-3.0.0-bundle.jar http://sourceforge.net/projects/jasperreports http://sourceforge.net/project/memberlist.php?group_id=36382 Open Source Reporting Engine -- 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: (MECLIPSE-397) Eclipse project set as dependency + test-jar dependency is included twice in .classpath
[ http://jira.codehaus.org/browse/MECLIPSE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MECLIPSE-397. Assignee: nicolas de loof Resolution: Fixed Fix Version/s: 2.5.2 The issue comes from the anti-duplicates ID : String depId = dep.getGroupId() + : + dep.getArtifactId() + : + dep.getClassifier() + : + dep.getVersion(); For dependencies referenced as eclipse project, the same ID must be generated for any classifier / version. Also applied the anti-duplicate principle to .project writer. Eclipse project set as dependency + test-jar dependency is included twice in .classpath --- Key: MECLIPSE-397 URL: http://jira.codehaus.org/browse/MECLIPSE-397 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: Core : Workspace settings Affects Versions: 2.5 Environment: maven 2.0.8, eclipse plugin version 2.5-20080218.113139-24 Reporter: nicolas de loof Assignee: nicolas de loof Fix For: 2.5.2 My maven project depends on A-util.jar for compile and A-util-tests.jar for tests : dependency groupId... artifactIdA-util/artifactId version... /dependency dependency groupId... artifactIdA-util/artifactId version... typetest-jar/type scopetest/scope /dependency I have the A-util project in my eclipse workspace Running mvn eclipse:eclipse creates an invalid .classpath where the eclipse A project is included twice : classpathentry kind=src path=/A-util/ classpathentry kind=src path=/A-util/ .. and invalid .project with twice references : projectA-util/project projectA-util/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] Commented: (MECLIPSE-397) Eclipse project set as dependency + test-jar dependency is included twice in .classpath
[ http://jira.codehaus.org/browse/MECLIPSE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135512#action_135512 ] nicolas de loof commented on MECLIPSE-397: -- fixed in 2.5.2-20080520.120258-2 Eclipse project set as dependency + test-jar dependency is included twice in .classpath --- Key: MECLIPSE-397 URL: http://jira.codehaus.org/browse/MECLIPSE-397 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: Core : Workspace settings Affects Versions: 2.5 Environment: maven 2.0.8, eclipse plugin version 2.5-20080218.113139-24 Reporter: nicolas de loof Assignee: nicolas de loof Fix For: 2.5.2 My maven project depends on A-util.jar for compile and A-util-tests.jar for tests : dependency groupId... artifactIdA-util/artifactId version... /dependency dependency groupId... artifactIdA-util/artifactId version... typetest-jar/type scopetest/scope /dependency I have the A-util project in my eclipse workspace Running mvn eclipse:eclipse creates an invalid .classpath where the eclipse A project is included twice : classpathentry kind=src path=/A-util/ classpathentry kind=src path=/A-util/ .. and invalid .project with twice references : projectA-util/project projectA-util/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-2068) Upload NeoDatis ODB
Upload NeoDatis ODB --- Key: MAVENUPLOAD-2068 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2068 Project: maven-upload-requests Issue Type: Wish Reporter: Antonio Petrelli Attachments: neodatis-odb-bundle.jar Please upload NeoDatis ODB, attached with this issue. NeoDatis ODB is a very simple Object Oriented Database for the Java platform. -- 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-65) filtered resources contains incorrect content
filtered resources contains incorrect content
-
Key: MRESOURCES-65
URL: http://jira.codehaus.org/browse/MRESOURCES-65
Project: Maven 2.x Resources Plugin
Issue Type: Bug
Affects Versions: 2.2
Reporter: Pappy Razvan STANESCU
Attachments: filtres.tar.gz
A project contains as resource the following Velocity template
\\
{code:none|title=src/main/resources/App.txt|borderStyle=solid}
${url}
${id}
${version}
${anotherProperty}
${infoBean.url}
${infoBean.id}
${infoBean.anotherProperty}
${infoBean.version}
${infoBean.myUrl}
${infoBean.myId}
${pom.version}
{code}
When filtering is set for this file the resulted output is wrong
{code:none|title=target/classes/App.txt|borderStyle=solid}
http://maven.apache.org
maven.bugs:filtres:jar:1.0-SNAPSHOT
1.0-SNAPSHOT
anotherValue
http://maven.apache.org
maven.bugs:filtres:jar:1.0-SNAPSHOT
${infoBean.anotherProperty}
1.0-SNAPSHOT
${infoBean.myUrl}
${infoBean.myId}
1.0-SNAPSHOT
{code}
\\
While it is acceptable to have ${pom.version} replaced or even ${id} or
${version}, the ${infoBean.*} lines should be left untouched as long as such
properties are not defined for the project.
A sample project is attached...
--
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-378) Allow additional types for scmVersionType
Allow additional types for scmVersionType - Key: SCM-378 URL: http://jira.codehaus.org/browse/SCM-378 Project: Maven SCM Issue Type: Improvement Components: maven-scm-api Affects Versions: future Reporter: Robert Egan Priority: Minor It would add greater flexibility to the product if there was support for additional versions of scmVersionType and scmVersion so that providers with more checkin/checkout options could easily support them. See related issue SCM-347 -- 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-2069) upload JPED repository to maven repository
upload JPED repository to maven repository -- Key: MAVENUPLOAD-2069 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2069 Project: maven-upload-requests Issue Type: Wish Reporter: David Delbecq Please sync jped internal release repository with maven central repository net.sf.jped,[EMAIL PROTECTED]:/home/groups/j/jp/jped/maven2/,rsync_ssh,David Delbecq,[EMAIL PROTECTED],, -- 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
Maven embedder issue
I am using MavenEmbedder 2.1 to parse my pom.xml. I have attached two files
with this mail.
One is my java program which is try to parse pom.xml and get MavenProject
out of it
Next one is my pom.xml.
My question is, how to pass runtime arguments to MavenEmbedder?
If you see in pom.xml, for one dependency I have mentioned $ variable which
will be resolved at runtime.
dependencies
dependency
groupIdcommons-io/groupId
artifactIdcommons-io/artifactId
version${dep.version}/version
scopecompile/scope
/dependency
/dependencies
This ${dep.version} is available as a property within pom.xml. If you see
the properties section, you can find dep.version
properties
dep.version${prop.version}/dep.version
/properties
Value for this dep.version is ${prop.version} which will be resolved only at
runtime. If we are using maven from command prompt, then we can run install
goal like this
mvn install -Dprop.version=1.2
Maven will resolve the ${prop.version} using command line parameters.
I just to want to know how to pass this in Maven Embedder.
Actually using Configuration class we can set system properties. In this
case System property get appended to JVM System property which will affect
our multi threaded build process (Our build machine sit on top up of solaris
box where only one JVM is running and build process is a multi threaded one)
If a system property is added to JVM, then it will have an effect on all
other threads which are simulatenously running)
http://www.nabble.com/file/p15152376/pom.xml pom.xml
http://www.nabble.com/file/p15152376/PomDetails.java PomDetails.java
--
View this message in context:
http://www.nabble.com/Maven-embedder-issue-tp15152376p15152376.html
Sent from the Maven - Issues mailing list archive at Nabble.com.
[jira] Commented: (MECLIPSE-437) Ordering of .classpath entries when using a newer version of JARs already included in the JDK.
[ http://jira.codehaus.org/browse/MECLIPSE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135522#action_135522 ] Max Bowsher commented on MECLIPSE-437: -- Ideally this would be configurable in the POM, since a static list of id patterns in the plugin is never going to satisfy everyone. What about a beforeJreDependencies element which takes a list of groupId:artifactId wildcard-capable patterns, in the manner used in other maven plugins? Is it worth reopening this issue or filing a new one? Ordering of .classpath entries when using a newer version of JARs already included in the JDK. -- Key: MECLIPSE-437 URL: http://jira.codehaus.org/browse/MECLIPSE-437 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Affects Versions: 2.4 Environment: WinXP, Maven 2.0.7 Reporter: Patrick Zeising Assignee: nicolas de loof Fix For: 2.5.2 While using a newer version of JaxWS (https://jax-ws.dev.java.net/) than the one supplied with JDK6 the generated .classpath file in my project directory contains all relevant entries headed by the entry for the JRE container. ---CODE--- classpath classpathentry kind=src path=src/main/java/ classpathentry kind=output path=target/classes/ classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ classpathentry kind=var path=M2_REPO/commons-lang/commons-lang/2.3/commons-lang-2.3.jar sourcepath=M2_REPO/commons-lang/commons-lang/2.3/commons-lang-2.3-sources.jar/ !-- MORE ENTRIES -- classpathentry kind=var path=M2_REPO/dev/java/net/jaxws-api/2.1.1/jaxws-api-2.1.1.jar/ !-- EVEN MORE ENTRIES -- classpathentry kind=var path=M2_REPO/commons-logging/commons-logging/1.1/commons-logging-1.1.jar sourcepath=M2_REPO/commons-logging/commons-logging/1.1/commons-logging-1.1-sources.jar/ /classpath ---/CODE--- As long as the JRE_CONTAINER is mentioned and loaded first my project will not compile in Eclipse since I am using operations unique to the newer version of JaxWS. When I set the order of the classpath entries in Eclipse manually (Properties - Java Build Path - Order and Export, setting the entry for JRE_CONTAINER to the 'bottom') my project will compile of course. Nicolas de Loof suggested the following in my post to the maven users mailing list (http://www.nabble.com/Maven2-Eclipse-Plugin---ordering-of-.classpath-entries-p16722527s177.html): ---CITE--- Maybe the eclipse plugin could detect java* and javax* groupIds and force them as toplevel ? This would require : - improve EclipseConfigWriter to have a new getJavaApiDeps(), and remove those deps from getDepsOrdered - improve EclipseClasspathWriter to write getJavaApiDeps prior to the JRE container. ---/CITE--- -- 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-437) Ordering of .classpath entries when using a newer version of JARs already included in the JDK.
[ http://jira.codehaus.org/browse/MECLIPSE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135524#action_135524 ] nicolas de loof commented on MECLIPSE-437: -- You're right this might be more configurable / extensible, but just consider this as a workaround waiting for eclipse to fix this. Ordering of .classpath entries when using a newer version of JARs already included in the JDK. -- Key: MECLIPSE-437 URL: http://jira.codehaus.org/browse/MECLIPSE-437 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Affects Versions: 2.4 Environment: WinXP, Maven 2.0.7 Reporter: Patrick Zeising Assignee: nicolas de loof Fix For: 2.5.2 While using a newer version of JaxWS (https://jax-ws.dev.java.net/) than the one supplied with JDK6 the generated .classpath file in my project directory contains all relevant entries headed by the entry for the JRE container. ---CODE--- classpath classpathentry kind=src path=src/main/java/ classpathentry kind=output path=target/classes/ classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ classpathentry kind=var path=M2_REPO/commons-lang/commons-lang/2.3/commons-lang-2.3.jar sourcepath=M2_REPO/commons-lang/commons-lang/2.3/commons-lang-2.3-sources.jar/ !-- MORE ENTRIES -- classpathentry kind=var path=M2_REPO/dev/java/net/jaxws-api/2.1.1/jaxws-api-2.1.1.jar/ !-- EVEN MORE ENTRIES -- classpathentry kind=var path=M2_REPO/commons-logging/commons-logging/1.1/commons-logging-1.1.jar sourcepath=M2_REPO/commons-logging/commons-logging/1.1/commons-logging-1.1-sources.jar/ /classpath ---/CODE--- As long as the JRE_CONTAINER is mentioned and loaded first my project will not compile in Eclipse since I am using operations unique to the newer version of JaxWS. When I set the order of the classpath entries in Eclipse manually (Properties - Java Build Path - Order and Export, setting the entry for JRE_CONTAINER to the 'bottom') my project will compile of course. Nicolas de Loof suggested the following in my post to the maven users mailing list (http://www.nabble.com/Maven2-Eclipse-Plugin---ordering-of-.classpath-entries-p16722527s177.html): ---CITE--- Maybe the eclipse plugin could detect java* and javax* groupIds and force them as toplevel ? This would require : - improve EclipseConfigWriter to have a new getJavaApiDeps(), and remove those deps from getDepsOrdered - improve EclipseClasspathWriter to write getJavaApiDeps prior to the JRE container. ---/CITE--- -- 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-499) Can't use -Dmaven.repo.local=tmp in multi-module reactor when useSystemClassLoader=false
Can't use -Dmaven.repo.local=tmp in multi-module reactor when useSystemClassLoader=false Key: SUREFIRE-499 URL: http://jira.codehaus.org/browse/SUREFIRE-499 Project: Maven Surefire Issue Type: Bug Components: process forking Affects Versions: 2.4.3 Reporter: Dan Fabulich At Redfin, we often launch builds with -Dmaven.repo.local=tmp (that is, temporarily put the local repo in the root of the build dir) to guarantee reproducibility. In a reactor build, we launch the sub-process and modify user.dir to be the dir of the leaf projects. When useSystemClassLoader=false, the IsolatedClassLoader thinks that the local repo is in parent/child/tmp rather than parent/tmp; as a result, the ICL fails to load any classes out of the local repository. The fix should be to make the classpath absolute rather than passing relative paths to the launched process. This might be a Maven core bug, or it might be possible to handle it in the plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEAR-73) Property to disable transitive dependencies resolving
[
http://jira.codehaus.org/browse/MEAR-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135531#action_135531
]
Stephane Nicoll commented on MEAR-73:
-
It's missing test cases so I need to write them first. But that sounds
reasonable indeed. It's just not complete as a patch for now.
Property to disable transitive dependencies resolving
-
Key: MEAR-73
URL: http://jira.codehaus.org/browse/MEAR-73
Project: Maven 2.x Ear Plugin
Issue Type: Improvement
Reporter: Thomas Hart
Assignee: Stephane Nicoll
Attachments: ear.jpg, patch.txt, patch2.txt
We have ears with a lot of modules. So the transitive dependencies are very
huge and to exclude all these with {{excludedtrue/excluded}} is no
option. Also to mark these dependencies with optional is no way. It is
possible to create a new property for that?
--
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-3580) FATAL ERROR and NPE on start
[ http://jira.codehaus.org/browse/MNG-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135539#action_135539 ] Erik Putrycz commented on MNG-3580: --- It might be a jdk specific bug, the same execution works with the sun jdk. FATAL ERROR and NPE on start Key: MNG-3580 URL: http://jira.codehaus.org/browse/MNG-3580 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.9 Environment: Linux iitm50ws1106 2.6.25.3-2-default #1 SMP 2008-05-10 07:46:36 +0200 x86_64 x86_64 x86_64 GNU/Linux java version 1.6.0 Java(TM) SE Runtime Environment (build pxa6460sr1-20080416_01(SR1)) IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460-20080415_18762 (JIT enabled, AOT enabled) J9VM - 20080415_018762_LHdSMr JIT - r9_20080415_1520 GC - 20080415_AA) JCL - 20080412_01 Reporter: Erik Putrycz Attachments: maven.log Any mvn command does give me the following error message [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Business Rules Extractor [INFO] Business Rules Extractor core functions [INFO] COBOL Parser and ANTLR Tools [INFO] Business Rules Extractor data model [INFO] Documentation Extractor module [INFO] Extractor module [INFO] Business Rules Navigator WAGON_VERSION: 1.0-beta-2 [INFO] [INFO] Building Business Rules Extractor [INFO]task-segment: [install] [INFO] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.project.ModelUtils.mergePluginLists(ModelUtils.java:164) at org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler.assembleBuildInheritance(DefaultModelInheritanceAssembler.java:366) at org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler.assembleModelInheritance(DefaultModelInheritanceAssembler.java:168) at org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler.assembleModelInheritance(DefaultModelInheritanceAssembler.java:61) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:852) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:253) at org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:265) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:197) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1542) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1033) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:997) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:477) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:59) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:39) at java.lang.reflect.Method.invoke(Method.java:612) 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) [INFO]
[jira] Updated: (MNG-3580) FATAL ERROR and NPE on start
[ http://jira.codehaus.org/browse/MNG-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Putrycz updated MNG-3580: -- Attachment: maven.log FATAL ERROR and NPE on start Key: MNG-3580 URL: http://jira.codehaus.org/browse/MNG-3580 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.9 Environment: Linux iitm50ws1106 2.6.25.3-2-default #1 SMP 2008-05-10 07:46:36 +0200 x86_64 x86_64 x86_64 GNU/Linux java version 1.6.0 Java(TM) SE Runtime Environment (build pxa6460sr1-20080416_01(SR1)) IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460-20080415_18762 (JIT enabled, AOT enabled) J9VM - 20080415_018762_LHdSMr JIT - r9_20080415_1520 GC - 20080415_AA) JCL - 20080412_01 Reporter: Erik Putrycz Attachments: maven.log Any mvn command does give me the following error message [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Business Rules Extractor [INFO] Business Rules Extractor core functions [INFO] COBOL Parser and ANTLR Tools [INFO] Business Rules Extractor data model [INFO] Documentation Extractor module [INFO] Extractor module [INFO] Business Rules Navigator WAGON_VERSION: 1.0-beta-2 [INFO] [INFO] Building Business Rules Extractor [INFO]task-segment: [install] [INFO] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.project.ModelUtils.mergePluginLists(ModelUtils.java:164) at org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler.assembleBuildInheritance(DefaultModelInheritanceAssembler.java:366) at org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler.assembleModelInheritance(DefaultModelInheritanceAssembler.java:168) at org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler.assembleModelInheritance(DefaultModelInheritanceAssembler.java:61) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:852) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:253) at org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:265) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:197) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1542) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1033) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:997) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:477) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:59) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:39) at java.lang.reflect.Method.invoke(Method.java:612) 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) [INFO] [INFO] Total time: 1 second [INFO] Finished at: Fri
[jira] Created: (NMAVEN-122) JavaBinding (solution generation) plugin needs a Clean goal
JavaBinding (solution generation) plugin needs a Clean goal --- Key: NMAVEN-122 URL: http://jira.codehaus.org/browse/NMAVEN-122 Project: NMaven Issue Type: New Feature Affects Versions: 0.14 (Unreleased) Reporter: Wendy Smoak Priority: Minor The JavaBinding plugin's Solution goal generates .sln and .csproj (or .vbproj) files. It would be nice to have a companion Clean goal to delete them. (Similar to mvn idea:idea and mvn idea:clean) -- 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-2070) rsync_ssh request for caelum-stella.sourceforge.net
rsync_ssh request for caelum-stella.sourceforge.net --- Key: MAVENUPLOAD-2070 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2070 Project: maven-upload-requests Issue Type: Wish Reporter: Cauê Haucke Porta Guerra net.sf.caelum-stella,[EMAIL PROTECTED]:/home/groups/c/ca/caelum-stella/htdocs/m2repo,rsync_ssh,Caue Guerra,[EMAIL PROTECTED],, Project page generated by maven hosted at project domain: http://stella.caelum.com.br/dev/team-list.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: (MNG-2068) Multiple inheritance fails to find grand parent in ../../pom.xml when the groupIds differ (Test Case Attached)
[ http://jira.codehaus.org/browse/MNG-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MNG-2068: --- Fix Version/s: (was: 2.0.x) 2.0.10 Multiple inheritance fails to find grand parent in ../../pom.xml when the groupIds differ (Test Case Attached) Key: MNG-2068 URL: http://jira.codehaus.org/browse/MNG-2068 Project: Maven 2 Issue Type: Bug Components: Inheritance and Interpolation Affects Versions: 2.0.4, 2.0.5, 2.0.6 Reporter: Brian Fox Assignee: John Casey Priority: Critical Fix For: 2.0.10 Attachments: good-sample.zip, mavenbugreport.zip, sample.zip I have a project that inherits from 2 (or more) parents. If the grand parent (parent of my parent) isn't in the repository, it isn't found at ../../pom.xml In my sample, make sure none of the artifacts are in your repository, then go down to sample-jar and try to build from there. See it fail. Note: If you remove the .sub from the second parent's group and update the sampe-jar pom, it no longer fails and finds the grandparent. See below for the output when the groups are different (fails) and when they are the same (works) Failing output: E:\sample\sample\sample-parent2\sample-jarmvn -X compile + Error stacktraces are turned on. [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settin gs\brianf\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'c:\PROGRA~1\MAVEN-~1. 2\bin\..\conf\plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for project : null:sample-jar:jar:null [DEBUG] Invalid parent-POM referenced by relative path '../pom.xml' in parent sp ecification in null:sample-parent2:pom:null: Specified: sample-project.sub:sample-parent::SNAPSHOT Found: sample-project:sample-parent:pom:SNAPSHOT [DEBUG] Retrieving parent-POM from the repository for project: null:sample-paren t2:pom:null [DEBUG] Skipping disabled repository central [DEBUG] sample-parent: using locally installed snapshot [DEBUG] Trying repository sv1-int Downloading: http://sv1.tus.stchome.com:9998/repository/sample-project/sub/sampl e-parent/SNAPSHOT/sample-parent-SNAPSHOT.pom [WARNING] Unable to get resource from repository sv1-int (http://sv1.tus.stchome .com:9998/repository) [DEBUG] Trying repository Maven Snapshots Downloading: http://snapshots.maven.codehaus.org/maven2//sample-project/sub/samp le-parent/SNAPSHOT/sample-parent-SNAPSHOT.pom [WARNING] Unable to get resource from repository Maven Snapshots (http://snapsho ts.maven.codehaus.org/maven2/) [DEBUG] Skipping disabled repository central [INFO] - --- [ERROR] FATAL ERROR [INFO] - --- [INFO] Failed to resolve artifact. GroupId: sample-project.sub ArtifactId: sample-parent Version: SNAPSHOT Reason: Unable to download the artifact from any repository sample-project.sub:sample-parent:pom:SNAPSHOT OUTPUT WITHOUT .sub: E:\sample\sample\sample-parent2\sample-jarmvn -X compile + Error stacktraces are turned on. [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settin gs\brianf\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'c:\PROGRA~1\MAVEN-~1. 2\bin\..\conf\plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for project : null:sample-jar:jar:null [DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for project : null:sample-parent2:pom:null [INFO] - --- [INFO] Building Maven Quick Start Archetype [INFO]task-segment: [compile] [INFO] - --- [DEBUG] maven-resources-plugin: resolved to version 2.1 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-resour -- 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-2071) rsync_ssh request for seleniumdsl.sourceforge.net
rsync_ssh request for seleniumdsl.sourceforge.net - Key: MAVENUPLOAD-2071 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2071 Project: maven-upload-requests Issue Type: Wish Reporter: Cauê Haucke Porta Guerra net.sf.seleniumdsl,[EMAIL PROTECTED]:/home/groups/s/se/seleniumdsl/htdocs/m2repo,rsync_ssh,Caue Guerra,[EMAIL PROTECTED],, Project page generated by maven hosted at project domain: http://seleniumdsl.sourceforge.net/team-list.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: (MAVENUPLOAD-2071) rsync_ssh request for seleniumdsl.sourceforge.net
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135550#action_135550 ] Cauê Haucke Porta Guerra commented on MAVENUPLOAD-2071: --- I have made a mistake, sorry about that the line should be: net.sf.seleniumdsl,[EMAIL PROTECTED]:/home/groups/s/se/seleniumdsl/htdocs/maven,rsync_ssh,Caue Guerra,[EMAIL PROTECTED],, rsync_ssh request for seleniumdsl.sourceforge.net - Key: MAVENUPLOAD-2071 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2071 Project: maven-upload-requests Issue Type: Wish Reporter: Cauê Haucke Porta Guerra net.sf.seleniumdsl,[EMAIL PROTECTED]:/home/groups/s/se/seleniumdsl/htdocs/m2repo,rsync_ssh,Caue Guerra,[EMAIL PROTECTED],, Project page generated by maven hosted at project domain: http://seleniumdsl.sourceforge.net/team-list.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: (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-tabpanelfocusedCommentId=135553#action_135553 ] Herve Boutemy commented on MANTTASKS-87: ok, you finished convincing me,and you gave me sufficient testcase to work on this issue again: please reopen... bq. the question is why use a different way of dealing with poms when it's a parent? this is a workaround that solved some issues with parent pom But it seems to cause other problems in other conditions. I'll have to work on it once more... 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.7 Environment: WindowsXP Ant version 1.7.0 Reporter: Jeff Campbell Assignee: Herve Boutemy Priority: Blocker Fix For: 2.0.8 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 project xmlns=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; modelVersion4.0.0/modelVersion groupIdintuit.sbconnect/groupId artifactIdsbclogin/artifactId version1.0.3/version nameSBCLogin/name parent groupIdmygroup/groupId artifactIdCommonPOM/artifactId version1.0.2/version /parent dependencies dependency groupIdmyothergroup/groupId artifactIdmyartifact/artifactId version1.0/version /dependency /dependencies /project Line in Ant build.xml file that causes the error: artifact:pom id=maven.project file=pom.xml/ 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] Created: (WAGON-210) Handle protocol names case-insensitively
Handle protocol names case-insensitively Key: WAGON-210 URL: http://jira.codehaus.org/browse/WAGON-210 Project: Maven Wagon Issue Type: Bug Components: wagon-provider-api Affects Versions: 1.0-beta-2 Reporter: Benjamin Bentmann Priority: Minor Attachments: case-insensitive-protocol.patch From [RFC 2396|http://www.ietf.org/rfc/rfc2396.txt], section 3.1, Scheme Component: bq. [...] programs interpreting URI should treat upper case letters as equivalent to lower case in scheme names (e.g., allow HTTP as well as http). -- 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-2072) Upload FCKeditor.Java 2.4. Beta 1
Upload FCKeditor.Java 2.4. Beta 1 - Key: MAVENUPLOAD-2072 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2072 Project: maven-upload-requests Issue Type: New Feature Reporter: Michael Osipov net.fckeditor,rsync://java.fckeditor.net/m2repo,rsync,Michael Osipov,[EMAIL PROTECTED],, -- 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: (MSITE-327) Use Doxia 1.0-alpha-11
Use Doxia 1.0-alpha-11 -- Key: MSITE-327 URL: http://jira.codehaus.org/browse/MSITE-327 Project: Maven 2.x Site Plugin Issue Type: Task Affects Versions: 2.0-beta-6 Reporter: Dennis Lundberg -- 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: (MSITE-327) Use Doxia 1.0-alpha-11
[ http://jira.codehaus.org/browse/MSITE-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-327: -- Assignee: Dennis Lundberg Fix Version/s: 2.0-beta-7 Use Doxia 1.0-alpha-11 -- Key: MSITE-327 URL: http://jira.codehaus.org/browse/MSITE-327 Project: Maven 2.x Site Plugin Issue Type: Task Affects Versions: 2.0-beta-6 Reporter: Dennis Lundberg Assignee: Dennis Lundberg Fix For: 2.0-beta-7 -- 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: (MSITE-242) remove copy of plexus-utils sources from site plugin sources since it is a dependency
[ http://jira.codehaus.org/browse/MSITE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-242: -- Fix Version/s: (was: 2.0-beta-7) 2.0-beta-8 remove copy of plexus-utils sources from site plugin sources since it is a dependency - Key: MSITE-242 URL: http://jira.codehaus.org/browse/MSITE-242 Project: Maven 2.x Site Plugin Issue Type: Task Affects Versions: 2.0-beta-6 Reporter: Herve Boutemy Assignee: Dennis Lundberg Fix For: 2.0-beta-8 the dependency has been uncommented, but the source code copy hasn't been removed classes copied are: - o.c.p.u.cli - o.c.p.u.interpolation - o.c.p.u.introspection - o.c.p.u.xml (partial: XML encoding support) -- 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: (MSITE-30) site:deploy incompatibilities with m1.02
[ http://jira.codehaus.org/browse/MSITE-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-30: - Fix Version/s: (was: 2.0-beta-7) 2.0-beta-8 site:deploy incompatibilities with m1.02 Key: MSITE-30 URL: http://jira.codehaus.org/browse/MSITE-30 Project: Maven 2.x Site Plugin Issue Type: Bug Components: site:deploy Environment: All Reporter: Paul Spencer Fix For: 2.0-beta-8 Deploying a site in m2 has changed since m1. 1) m1 used the tar and gunzip command on the remote site, where m2 uses the unzip command. This poses a problem for be since my remote site does not support the unzip command, thus making the priority of this issue major 1.1) Their may be desire to deploy without the use of tools like tar and zip on some site. The deploy would esentailly be a recersive copy 2) No equivelent to m1 property maven.site.chmod.mode. I use this to allow other member is the group update and delete permission 3) No equivelent to m1 property maven.site.publish.clean Their are other properties for the m1.02 not mentioned above, but I suspect the they can be calculated from m2 files, i.e. pom.xml and settings.xml. Paul Spencer -- 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: (MSITE-326) Make file encoding default to platform encoding
[ http://jira.codehaus.org/browse/MSITE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-326: -- Fix Version/s: (was: 2.0-beta-7) 2.0-beta-8 Make file encoding default to platform encoding --- Key: MSITE-326 URL: http://jira.codehaus.org/browse/MSITE-326 Project: Maven 2.x Site Plugin Issue Type: Wish Components: encoding Affects Versions: 2.0-beta-5, 2.0-beta-6 Reporter: Herve Boutemy Fix For: 2.0-beta-8 According to the [user poll about the default file encoding|http://www.nabble.com/-POLL--Default-Value-for-File-Encoding-td16958386.html], the inputEncoding and outputEncoding should default to the platform default encoding instead of Latin-1. Since that would be a breaking change it is left to users to vote for this issue if they feelt it's worth to have it like that. If the change is made, we should have the plugin output a warning when using the platform encoding. -- 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: (MSITE-3) site adds relative paths to css, etc, but doesn't work for error documents
[ http://jira.codehaus.org/browse/MSITE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-3: Fix Version/s: (was: 2.0-beta-7) 2.0-beta-8 site adds relative paths to css, etc, but doesn't work for error documents -- Key: MSITE-3 URL: http://jira.codehaus.org/browse/MSITE-3 Project: Maven 2.x Site Plugin Issue Type: Bug Components: relative links Reporter: Brett Porter Fix For: 2.0-beta-8 we should possibly use the absolute urls for these anyway. -- 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: (MSITE-141) Possible security hole when deploying site
[ http://jira.codehaus.org/browse/MSITE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-141: -- Fix Version/s: (was: 2.0-beta-7) 2.0-beta-8 Possible security hole when deploying site -- Key: MSITE-141 URL: http://jira.codehaus.org/browse/MSITE-141 Project: Maven 2.x Site Plugin Issue Type: Bug Components: site:deploy Affects Versions: 2.0-beta-5 Environment: Linux gentoo 2.6.16 64bit, maven 2.0.2 Reporter: Martin Vysny Priority: Critical Fix For: 2.0-beta-8 When the site is deployed into a directory /foo/bar, the following command is issued over a ssh: chmod -Rf g+w /foo/bar/ it was intended to use g+r I presume? :-) -- 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: (MSITE-177) Docs are not updated if only site.xml changed
[ http://jira.codehaus.org/browse/MSITE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-177: -- Fix Version/s: (was: 2.0-beta-7) 2.0-beta-8 Docs are not updated if only site.xml changed - Key: MSITE-177 URL: http://jira.codehaus.org/browse/MSITE-177 Project: Maven 2.x Site Plugin Issue Type: Bug Components: site descriptor Affects Versions: 2.0-beta-5 Reporter: Jörg Hohwiller Fix For: 2.0-beta-8 If I update site.xml (e.g. add new menu-items) and regenerate my existing site, the index gets updated but other existing pages are not rebuild and therefore show the menus in the state before the site.xml has changed (so new menus are missing). This causes a confusing site where menus appear and disappear while surfing. I only use xdos (and they are in a subfolder) so I can not tell if this happens with apt as well. I reproduced the problem with mvn site and mvn site:stage. As a workaround I can delete the old site before building. Since I stage the site directly to the final destination on the local machine where it is served this is not very suitable because then the site is broken until it is completely rebuild. If you consider to fix this issue please beware that site.xml can inherit stuff in multiproject envronments. So it is unclear if the optimization to only re-generate if something has changed makes sense at all. It might be quite complicated to determine this - the question is how much time is saved by this at all. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-300) Using maven-shade-plugin instead of forking plexus-utils
[ http://jira.codehaus.org/browse/MSITE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-300: -- Fix Version/s: (was: 2.0-beta-7) 2.0-beta-8 Using maven-shade-plugin instead of forking plexus-utils Key: MSITE-300 URL: http://jira.codehaus.org/browse/MSITE-300 Project: Maven 2.x Site Plugin Issue Type: Sub-task Affects Versions: 2.0-beta-6 Reporter: Vincent Siveton Fix For: 2.0-beta-8 -- 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: (MSITE-206) Move the webapp features to a separate plugin
[ http://jira.codehaus.org/browse/MSITE-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-206: -- Fix Version/s: (was: 2.0-beta-7) 2.0-beta-8 Move the webapp features to a separate plugin - Key: MSITE-206 URL: http://jira.codehaus.org/browse/MSITE-206 Project: Maven 2.x Site Plugin Issue Type: Improvement Components: site:run Affects Versions: 2.0-beta-5 Reporter: Jason van Zyl Assignee: Jason van Zyl Fix For: 2.0-beta-8 Prevent the complete download of Jetty for rendering the site and move to a separate plugin. -- 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: (MSITE-150) Inconsistent navigational mechanisms: If project defines its own index page (e.g. apt/index.apt) the Project Information-About link is missing.
[ http://jira.codehaus.org/browse/MSITE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-150: -- Fix Version/s: (was: 2.0-beta-7) 2.0-beta-8 Inconsistent navigational mechanisms: If project defines its own index page (e.g. apt/index.apt) the Project Information-About link is missing. Key: MSITE-150 URL: http://jira.codehaus.org/browse/MSITE-150 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.0-beta-5 Environment: 2.0.4, JDK14, XP Reporter: John Allen Fix For: 2.0-beta-8 If project defines its own index page (e.g. apt/index.apt) the Project Information-About link is removed. I can see the argument that states 'if youve developed your own front page you can define the index to it yourself' but this just results in inconsistencies in the navigational mechanisms used in maven generated sites. If one of my projects provides its own index page then you will have to browse to it via some new menu based link and for all the other projects you can get to it via the About link. I think About should always link to index.apt. Note: apologies if this is a MPIR issue, its manifested by running site so ive raised it in 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: (MSITE-82) M2 Site Plugin too strict about document structure
[ http://jira.codehaus.org/browse/MSITE-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-82: - Fix Version/s: (was: 2.0-beta-7) 2.0-beta-8 M2 Site Plugin too strict about document structure -- Key: MSITE-82 URL: http://jira.codehaus.org/browse/MSITE-82 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.0-beta-4 Environment: Java 1.5, WinXP SP2 Reporter: John R Fallows Fix For: 2.0-beta-8 Site generation generally assumes total ownership of the generated HTML content, such that complete HTML pages are expected to be generated. Therefore, strict rules are specified when parsing APT documentation files as input to site generation process, to make sure that APT files have full page structure. Unfortunately, this restriction is too brittle for Java.Net based Maven2 projects that want to generate site documentation. Java.Net adds chrome dynamically at runtime to all pages (not a problem) but it also adds a project summary and a header for the project Description around any HTML content in the top level index.html page for a project. This means that the generated index.html page needs to have a structure such as p.../ph2Next Section/h2p.../p. As you can see, this is not a valid HTML document, but an HTML fragments. Unfortunately, the APT parser is too strict to support the corresponding index.apt syntax logically required to produce such an index.html. Please allow the syntax checking during parsing to be relaxed as necessary to achieve the desired generated HTML. As mentioned by Brett, we could support out-of-order elements, but with warnings This might be generally useful for fragment generation in general, anywhere a server-side include could be used by the generated site. However, if we take this approach, it would be useful to be able to still get a clean build with no warnings, possibly by specifying which site files are fragments so that warnings could still be generated for user errors in other non-fragment pages. Perhaps the .aptf extension could be used to indicate a fragment APT file. -- 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: (MSITE-47) validate input format of docs
[ http://jira.codehaus.org/browse/MSITE-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-47: - Fix Version/s: (was: 2.0-beta-7) 2.0-beta-8 validate input format of docs - Key: MSITE-47 URL: http://jira.codehaus.org/browse/MSITE-47 Project: Maven 2.x Site Plugin Issue Type: Bug Reporter: Brett Porter Fix For: 2.0-beta-8 valid: - xdoc - apt (done on the fly) - fml - site.xml (most should be on the fly, verify that it handles appropriately). Perhaps make whether this is an error or ignored should be configurable -- 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: (MSITE-136) when inheriting site.xml the menu ref='parent' expands to a menu with links for *all* ancestors and not just the immediate parent
[ http://jira.codehaus.org/browse/MSITE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-136: -- Fix Version/s: (was: 2.0-beta-7) 2.0-beta-8 when inheriting site.xml the menu ref='parent' expands to a menu with links for *all* ancestors and not just the immediate parent --- Key: MSITE-136 URL: http://jira.codehaus.org/browse/MSITE-136 Project: Maven 2.x Site Plugin Issue Type: Bug Components: inheritance Affects Versions: 2.0-beta-5 Environment: 2.0.4 Reporter: John Allen Fix For: 2.0-beta-8 multi-project environment; root project provides site.xml root/sub1/sub2/sub3/sub4 site pages get rendered with parent menu containing links for all the ancestors and not just the immediate sub3 parent. copying root's site.xml into sub4 results in parent being correctly rendered. did not test the results of copying site.xml into the middle of the ancestry so cant say whether the parents list starts at the project that defines the site.xml -- 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: (MSITE-163) The modules menu is not inherited
[ http://jira.codehaus.org/browse/MSITE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-163: -- Fix Version/s: (was: 2.0-beta-7) 2.0-beta-8 The modules menu is not inherited - Key: MSITE-163 URL: http://jira.codehaus.org/browse/MSITE-163 Project: Maven 2.x Site Plugin Issue Type: Bug Components: inheritance Affects Versions: 2.0-beta-4 Environment: ubuntu linux / debian linux Reporter: Andrew Williams Fix For: 2.0-beta-8 if I have a site.xml in a parent project that contains the line menu ref=modules inherit=top / it is not inherited by child projects. menu ref=reports inherit=top / works, as does parent. This happens when the parent project has no modules of its own. -- 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: (MSITE-79) mechanism for local preview of a multiproject site tree
[ http://jira.codehaus.org/browse/MSITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-79: - Fix Version/s: (was: 2.0-beta-7) 2.0-beta-8 mechanism for local preview of a multiproject site tree --- Key: MSITE-79 URL: http://jira.codehaus.org/browse/MSITE-79 Project: Maven 2.x Site Plugin Issue Type: New Feature Components: site:run Reporter: Brett Porter Fix For: 2.0-beta-8 currently difficult as they are in target/site/*, where the links rely on ./ -- 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: (MSITE-298) Bump to Doxia 1.0-beta-1-SNAPSHOT
[ http://jira.codehaus.org/browse/MSITE-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-298: -- Fix Version/s: (was: 2.0-beta-7) 2.0-beta-8 Bump to Doxia 1.0-beta-1-SNAPSHOT - Key: MSITE-298 URL: http://jira.codehaus.org/browse/MSITE-298 Project: Maven 2.x Site Plugin Issue Type: Task Affects Versions: 2.0-beta-6 Reporter: Vincent Siveton Fix For: 2.0-beta-8 -- 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: (MSITE-81) Site descriptor resolution never falls back to site.xml
[ http://jira.codehaus.org/browse/MSITE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-81: - Fix Version/s: (was: 2.0-beta-7) 2.0-beta-8 Site descriptor resolution never falls back to site.xml --- Key: MSITE-81 URL: http://jira.codehaus.org/browse/MSITE-81 Project: Maven 2.x Site Plugin Issue Type: Bug Components: site descriptor Reporter: Indrajit Raychaudhuri Priority: Critical Fix For: 2.0-beta-8 Attachments: site.log, sitemojo.patch For default locale (i.e., Locale.getDefault() is en) site descriptor for parent project attempt to resolve site_en.xml. But it doesn't fallback to site.xml. -- 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: (MSITE-289) site:run in maven's site/trunk doesn't show certain apt files
[ http://jira.codehaus.org/browse/MSITE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-289: -- Fix Version/s: (was: 2.0-beta-7) 2.0-beta-8 site:run in maven's site/trunk doesn't show certain apt files - Key: MSITE-289 URL: http://jira.codehaus.org/browse/MSITE-289 Project: Maven 2.x Site Plugin Issue Type: Bug Components: site:run Affects Versions: 2.0-beta-6 Reporter: Dan Fabulich Fix For: 2.0-beta-8 Pull down https://svn.apache.org/repos/asf/maven/site/trunk at revision 612559 and do mvn site:run. Now examine http://localhost:8080/guides/introduction/introduction-to-dependency-mechanism.html You'll get a 404 error. But the apt file is clearly there, and it works fine if you mvn site and then navigate to target/site/guides/introduction/introduction-to-dependency-mechanism.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: (MSITE-194) xdoc's head/ gets rendered in the HTML body, not in head
[ http://jira.codehaus.org/browse/MSITE-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-194: -- Fix Version/s: (was: 2.0-beta-7) 2.0-beta-8 xdoc's head/ gets rendered in the HTML body, not in head -- Key: MSITE-194 URL: http://jira.codehaus.org/browse/MSITE-194 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.0-beta-5 Reporter: Brett Porter Fix For: 2.0-beta-8 -- 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: (MSITE-327) Use Doxia 1.0-alpha-11
[ http://jira.codehaus.org/browse/MSITE-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-327. - Resolution: Fixed Fixed in r658451. Use Doxia 1.0-alpha-11 -- Key: MSITE-327 URL: http://jira.codehaus.org/browse/MSITE-327 Project: Maven 2.x Site Plugin Issue Type: Task Affects Versions: 2.0-beta-6 Reporter: Dennis Lundberg Assignee: Dennis Lundberg Fix For: 2.0-beta-7 -- 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-100) Use Doxia 1.0-alpha-11
[ http://jira.codehaus.org/browse/MPIR-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MPIR-100. Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 2.1 Fixed in r658457. Use Doxia 1.0-alpha-11 -- Key: MPIR-100 URL: http://jira.codehaus.org/browse/MPIR-100 Project: Maven 2.x Project Info Reports Plugin Issue Type: Task Affects Versions: 2.0.1 Reporter: Dennis Lundberg Assignee: Dennis Lundberg Fix For: 2.1 -- 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: (WAGON-111) UNC paths don't work when properly URL encoded.
[
http://jira.codehaus.org/browse/WAGON-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135563#action_135563
]
bentmann edited comment on WAGON-111 at 5/20/08 4:55 PM:
--
Some URL decoding that should help. BTW, I am just *guessing* that
{{Repository.getBasedir()}} is intended to return a valid filesystem path for
{{file:}} URLs. The fix for WAGON-112 still doesn't say anything about the
precise meaning of this string but all the voodoo in {{PathUtils.basedir()}}
seems to aim at constructing a local filesystem path
was (Author: bentmann):
Some URL decoding that should help.
UNC paths don't work when properly URL encoded.
---
Key: WAGON-111
URL: http://jira.codehaus.org/browse/WAGON-111
Project: Maven Wagon
Issue Type: Bug
Components: wagon-file
Affects Versions: 1.0-beta-2
Reporter: Josh Peters
Fix For: 1.x
Attachments: url-decoding.patch
Please see http://jira.codehaus.org/browse/MSITE-318 for a summary.
Essentially, it seems that Maven cannot grok URL encoded UNC paths with the
file:// scheme.
--
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: (MPIR-80) Add Java requirements to the Dependency Report
[ http://jira.codehaus.org/browse/MPIR-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MPIR-80: Fix Version/s: (was: 2.1) Add Java requirements to the Dependency Report -- Key: MPIR-80 URL: http://jira.codehaus.org/browse/MPIR-80 Project: Maven 2.x Project Info Reports Plugin Issue Type: New Feature Components: dependencies, summary Affects Versions: 2.0.1 Reporter: Niall Pemberton Attachments: maven-projectinfo-dependency-java-v2.patch, maven-projectinfo-dependency-java-v3.patch, maven-projectinfo-dependency-java.patch, maven-projectinfo-summary-java.patch It would be nice to add a section to the dependency report showing the java version requirements. Attaching a patch which discovers the java version and compiler options from the java-compiler-plugin configuration and outputs a Java Version section. Has an option to configure whether or not this section is shown (default to false). -- 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: (MJAVADOC-119) Aggregate does not work for multiple module project when doing install.
[ http://jira.codehaus.org/browse/MJAVADOC-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135568#action_135568 ] Paul Gier commented on MJAVADOC-119: Originally this issue was related to creating an aggregate javadoc jar, but this seems impossible now because of MJAVADOC-125. The javadoc plugin is skipped because the aggregate project has a packaging of pom. If there are no plans to allow aggregate javadoc generation during the standard install lifecycle, then I guess this issue should be closed as Will not fix. Aggregate does not work for multiple module project when doing install. --- Key: MJAVADOC-119 URL: http://jira.codehaus.org/browse/MJAVADOC-119 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.2 Environment: Fedora Linux, Maven 2.0.6 Reporter: Paul Gier Attachments: MJAVADOC-119-it.patch If have a multi-module project, the javadoc aggregate does not find inter-module dependencies: pom.xml |--gt;module1 |--gt;module2 module 1 depends on module 2 The javadoc plugin is added to the build lifecycle attached to the install phase. When I run mvn install I get a Failed to resolve artifact. error message looking for module 2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MJAVADOC-119) Aggregate does not work for multiple module project when doing install.
[ http://jira.codehaus.org/browse/MJAVADOC-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Gier updated MJAVADOC-119: --- Attachment: MJAVADOC-119-it.patch Adding IT that reproduces the issue. Aggregate does not work for multiple module project when doing install. --- Key: MJAVADOC-119 URL: http://jira.codehaus.org/browse/MJAVADOC-119 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.2 Environment: Fedora Linux, Maven 2.0.6 Reporter: Paul Gier Attachments: MJAVADOC-119-it.patch If have a multi-module project, the javadoc aggregate does not find inter-module dependencies: pom.xml |--gt;module1 |--gt;module2 module 1 depends on module 2 The javadoc plugin is added to the build lifecycle attached to the install phase. When I run mvn install I get a Failed to resolve artifact. error message looking for module 2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPIR-101) Update to Doxia 1.0-beta-1
Update to Doxia 1.0-beta-1 -- Key: MPIR-101 URL: http://jira.codehaus.org/browse/MPIR-101 Project: Maven 2.x Project Info Reports Plugin Issue Type: Task Affects Versions: 2.1 Reporter: Dennis Lundberg -- 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: (MSITE-298) Update to Doxia 1.0-beta-1
[ http://jira.codehaus.org/browse/MSITE-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-298: -- Summary: Update to Doxia 1.0-beta-1 (was: Bump to Doxia 1.0-beta-1-SNAPSHOT) Update to Doxia 1.0-beta-1 -- Key: MSITE-298 URL: http://jira.codehaus.org/browse/MSITE-298 Project: Maven 2.x Site Plugin Issue Type: Task Affects Versions: 2.0-beta-6 Reporter: Vincent Siveton Fix For: 2.0-beta-8 -- 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-2045) Upload SNMP4J 1.9.1e
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135569#action_135569 ] Paul Donohue commented on MAVENUPLOAD-2045: --- SNMP4J 1.9.1f and SNMP4J-Agent 1.2 have been released. Updated bundles: http://www.PaulSD.com/snmp4j-1.9.1f-bundle.jar http://www.PaulSD.com/snmp4j-agent-1.2-RC1-bundle.jar Upload SNMP4J 1.9.1e Key: MAVENUPLOAD-2045 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2045 Project: maven-upload-requests Issue Type: Wish Reporter: Paul Donohue http://www.PaulSD.com/snmp4j-1.9.1e-bundle.jar http://www.snmp4j.org/ I AM NOT an SNMP4J developer. I asked about updating the maven repo on the SNMP4J mailing list and received no response, so I assume they are ok with me requesting an update to the maven repo. 1.9.1e is the latest release. Thanks! -- 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: (MAVENUPLOAD-2045) Upload SNMP4J 1.9.1e
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135569#action_135569 ] topquark edited comment on MAVENUPLOAD-2045 at 5/20/08 5:38 PM: SNMP4J 1.9.1f and SNMP4J-Agent 1.2 have been released. Updated bundles: http://www.PaulSD.com/snmp4j-1.9.1f-bundle.jar http://www.PaulSD.com/snmp4j-agent-1.2-bundle.jar was (Author: topquark): SNMP4J 1.9.1f and SNMP4J-Agent 1.2 have been released. Updated bundles: http://www.PaulSD.com/snmp4j-1.9.1f-bundle.jar http://www.PaulSD.com/snmp4j-agent-1.2-RC1-bundle.jar Upload SNMP4J 1.9.1e Key: MAVENUPLOAD-2045 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2045 Project: maven-upload-requests Issue Type: Wish Reporter: Paul Donohue http://www.PaulSD.com/snmp4j-1.9.1e-bundle.jar http://www.snmp4j.org/ I AM NOT an SNMP4J developer. I asked about updating the maven repo on the SNMP4J mailing list and received no response, so I assume they are ok with me requesting an update to the maven repo. 1.9.1e is the latest release. Thanks! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (SCM-368) Windows path length limitations can be overcome by feeding an absolute path to SVN
[
http://jira.codehaus.org/browse/SCM-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy reopened SCM-368:
--
Hi,
The fix in rev [656441|http://svn.apache.org/viewvc?view=revrevision=656441]
breaks continuum on cygwin.
Relevant part of the log :
{code}
2008-05-21 00:28:26,265 [pool-1-thread-1] INFO org.apache.continuum.scm.manager
.Slf4jScmLogger - Executing: cmd.exe /X /C svn --non-interactive update
C:\ci\wd\41
2008-05-21 00:28:26,296 [pool-1-thread-1] INFO org.apache.continuum.scm.manager
.Slf4jScmLogger - Working directory: C:\ci\wd\41
2008-05-21 00:28:26,484 [pool-1-thread-1] INFO org.apache.continuum.scm.manager
.Slf4jScmLogger - Svn command failed due to some locks in working copy. We try
to run a 'svn cleanup'.
{code}
The workaround is too add windows svn first in the cygwin path.
Windows path length limitations can be overcome by feeding an absolute path
to SVN
--
Key: SCM-368
URL: http://jira.codehaus.org/browse/SCM-368
Project: Maven SCM
Issue Type: Improvement
Components: maven-scm-api
Affects Versions: 1.0
Environment: Any Windows machine
Reporter: Kurt Tometich
Assignee: Emmanuel Venisse
Priority: Minor
Fix For: 1.1
When calling Subversion with relative paths there is a limit of 255
characters to the path length. If you call Subversion with an absolute path
that no longer applies and you now have access to 32K chars. I have tried
this myself and it does work. Try feeding SVN a path that is relative and is
over 255 chars. It will not be able to complete the transaction. Now, try
to the same path again only as an absolute path and it will successfully
complete the transaction. Here is a link to the forum where I found this
information: http://en-us.www.mozilla.com/en-US/firefox/2.0.0.4/firstrun/.
--
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: (WAGON-165) scp-external-wagen and ssh using ProxyCommand blacklist repository
[ http://jira.codehaus.org/browse/WAGON-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-165. -- Assignee: Brett Porter Resolution: Fixed applied thanks scp-external-wagen and ssh using ProxyCommand blacklist repository - Key: WAGON-165 URL: http://jira.codehaus.org/browse/WAGON-165 Project: Maven Wagon Issue Type: Bug Components: wagon-ssh Environment: linux 2.6.15-1.2054_FC5 client ssh: OpenSSH_4.3p2, OpenSSL 0.9.8a 11 Oct 2005 server in the middle ssh:OpenSSH_4.2, OpenSSL 0.9.7d 17 Mar 2004 Reporter: M. van der Plas Assignee: Brett Porter Fix For: 1.0-beta-3 Attachments: EndsWith.patch I use my laptop to work at the office and at home. The office has a repository for inhouse developed projects. ssh channles are used to connect with the office repository from home. I configured ssh using with a ProcyCommand to tunnel to the subversion respository. I configured mvn using a home specific settings.xml to use scp-external-ssh as the standard ssh wagon cannot handle the ProxyCommand. This fails when external 3rd party artifacts and plugins are checked in the company repositories. Since they are located in the ibiblio central repository the scp command fails. This is normally not a problem because the Wagons check if the output of the copy command is No such file or directory. If so, the artifact is searched in another repository. With the introduction of the ProxyCommand this mechanism does not work any more. ProxyCommand prints Killed by signal 1 to stderr when the scp command fails. See also http://lists.debian.org/debian-ssh/2005/06/msg00074.html for the ssh bug. The problem is that both wagon-providers/wagon-ssh/src/main/java/org/apache/maven/wagon/providers/ssh/ScpWagon.java (revision 388735) and wagon-providers/wagon-ssh-external/src/main/java/org/apache/maven/wagon/providers/sshext/ScpExternalWagon.java (revision 388735) use stderr.endsWith(No such file or directory) while stderr in my case ends with Killed by sgnal 1. The problem can be fixed by using indexOf( No such file or directory) != -1 instead of the endsWith() call. I've implemented this fix and verified that the problem did not occur. The patch is attached. -- 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: (WAGON-210) Handle protocol names case-insensitively
[ http://jira.codehaus.org/browse/WAGON-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated WAGON-210: --- Fix Version/s: 1.0-beta-3 Handle protocol names case-insensitively Key: WAGON-210 URL: http://jira.codehaus.org/browse/WAGON-210 Project: Maven Wagon Issue Type: Bug Components: wagon-provider-api Affects Versions: 1.0-beta-2 Reporter: Benjamin Bentmann Priority: Minor Fix For: 1.0-beta-3 Attachments: case-insensitive-protocol.patch From [RFC 2396|http://www.ietf.org/rfc/rfc2396.txt], section 3.1, Scheme Component: bq. [...] programs interpreting URI should treat upper case letters as equivalent to lower case in scheme names (e.g., allow HTTP as well as http). -- 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: (NMAVEN-123) Remove maven 2.1 snapshot dependencies, embedder dependencies, war dependency in favor for System.Diagnostics.Process when running maven commands in VS
[ http://jira.codehaus.org/browse/NMAVEN-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan ancajas updated NMAVEN-123: --- Attachment: NMAVEN-123.patch attached patch Remove maven 2.1 snapshot dependencies, embedder dependencies, war dependency in favor for System.Diagnostics.Process when running maven commands in VS Key: NMAVEN-123 URL: http://jira.codehaus.org/browse/NMAVEN-123 Project: NMaven Issue Type: Improvement Affects Versions: 0.14 (Unreleased) Reporter: jan ancajas Attachments: NMAVEN-123.patch -- 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: (NMAVEN-123) Remove maven 2.1 snapshot dependencies, embedder dependencies, war dependency in favor for System.Diagnostics.Process when running maven commands in VS
Remove maven 2.1 snapshot dependencies, embedder dependencies, war dependency in favor for System.Diagnostics.Process when running maven commands in VS Key: NMAVEN-123 URL: http://jira.codehaus.org/browse/NMAVEN-123 Project: NMaven Issue Type: Improvement Affects Versions: 0.14 (Unreleased) Reporter: jan ancajas Attachments: NMAVEN-123.patch -- 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: (WAGON-210) Handle protocol names case-insensitively
[ http://jira.codehaus.org/browse/WAGON-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-210. -- Assignee: Brett Porter Resolution: Fixed applied. Feel free to also commit yourself :) Can we add unit tests for this? Handle protocol names case-insensitively Key: WAGON-210 URL: http://jira.codehaus.org/browse/WAGON-210 Project: Maven Wagon Issue Type: Bug Components: wagon-provider-api Affects Versions: 1.0-beta-2 Reporter: Benjamin Bentmann Assignee: Brett Porter Priority: Minor Fix For: 1.0-beta-3 Attachments: case-insensitive-protocol.patch From [RFC 2396|http://www.ietf.org/rfc/rfc2396.txt], section 3.1, Scheme Component: bq. [...] programs interpreting URI should treat upper case letters as equivalent to lower case in scheme names (e.g., allow HTTP as well as http). -- 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: (MSITE-129) modules list empty if modules don't use this project as parent in reactor build
[
http://jira.codehaus.org/browse/MSITE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135586#action_135586
]
Bugittaa Pahasti commented on MSITE-129:
The workaround isn't a feasible solution in a CI environment. Considering the
number of votes and watchers I would find this bug at least serious, not minor
as currently.
modules list empty if modules don't use this project as parent in reactor
build
---
Key: MSITE-129
URL: http://jira.codehaus.org/browse/MSITE-129
Project: Maven 2.x Site Plugin
Issue Type: Bug
Components: multi module
Affects Versions: 2.0-beta-5
Reporter: Kenney Westerhof
Assignee: Kenney Westerhof
Priority: Minor
Fix For: 2.0-beta-8
The code in the AbstractSiteRenderingMojo does the following:
- if it's running in a reactor build (i.e. more than 1 project in the reactor
projects) it scans all
projects to see if it's parent project equals the current project. If so,
it's marked as a module.
- if it's running on a single project, the project.build.modules is consulted
and those modules
are marked as modules.
I've got a 'fake' root pom, for utility purposes: it lists all projects as
modules so that I can easily
built everything and generate a site. However, this fake root pom is never
used as a parent - there's
a /pom/pom.xml project for that.
The result of this is that the modules list is empty.
A workaround is to first run 'mvn site' and then 'mvn site -N'.
I'm not sure what the correct solution should be - basically now 2 site
layouts are implemented:
- a physical layout where the modules match the modules section of the pom,
reflecting filesystem layout,
- a project hierarchy layout based on parent
and one or the other is used depending on wheter the build contains more than
1 project or not.
My first feeling is that since the tag is called ${modules} (or menu
ref=modules/) that
the site should use the modules, not the parent.
It should also take into consideration, that IF a reactor build is running,
it should only use the modules that are also
in the reactor (so you can use -r -Dmaven.reactor.excludes=.. to generate a
site with not all projects in it).
Thoughts?
--
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: (WAGON-210) Handle protocol names case-insensitively
[
http://jira.codehaus.org/browse/WAGON-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135587#action_135587
]
Benjamin Bentmann commented on WAGON-210:
-
bq. Feel free to also commit yourself
There is something special about Wagon it seems: {{403 Forbidden}}
Handle protocol names case-insensitively
Key: WAGON-210
URL: http://jira.codehaus.org/browse/WAGON-210
Project: Maven Wagon
Issue Type: Bug
Components: wagon-provider-api
Affects Versions: 1.0-beta-2
Reporter: Benjamin Bentmann
Assignee: Brett Porter
Priority: Minor
Fix For: 1.0-beta-3
Attachments: case-insensitive-protocol.patch
From [RFC 2396|http://www.ietf.org/rfc/rfc2396.txt], section 3.1, Scheme
Component:
bq. [...] programs interpreting URI should treat upper case letters as
equivalent to lower case in scheme names (e.g., allow HTTP as well as
http).
--
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: (WAGON-210) Handle protocol names case-insensitively
[ http://jira.codehaus.org/browse/WAGON-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135588#action_135588 ] Brett Porter commented on WAGON-210: are you using http instead of https? Handle protocol names case-insensitively Key: WAGON-210 URL: http://jira.codehaus.org/browse/WAGON-210 Project: Maven Wagon Issue Type: Bug Components: wagon-provider-api Affects Versions: 1.0-beta-2 Reporter: Benjamin Bentmann Assignee: Brett Porter Priority: Minor Fix For: 1.0-beta-3 Attachments: case-insensitive-protocol.patch From [RFC 2396|http://www.ietf.org/rfc/rfc2396.txt], section 3.1, Scheme Component: bq. [...] programs interpreting URI should treat upper case letters as equivalent to lower case in scheme names (e.g., allow HTTP as well as http). -- 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
