[jira] Commented: (MECLIPSE-411) manifest property usage is only for ogsi maifests
[ http://jira.codehaus.org/browse/MECLIPSE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128843#action_128843 ] Richard van Nieuwenhoven commented on MECLIPSE-411: --- just tested and it works, thanks! now to the vote. > manifest property usage is only for ogsi maifests > - > > Key: MECLIPSE-411 > URL: http://jira.codehaus.org/browse/MECLIPSE-411 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: OSGi, Manifest, WTP support >Affects Versions: 2.5 > Environment: any >Reporter: Richard van Nieuwenhoven >Assignee: Arnaud Heritier > Fix For: 2.5.1 > > Attachments: manifest.patch > > > the manifest property of the eclipse plugin is only for the osgi writer and > not for the wtp manifest, because the wtp manifest is a special case that > will not be included in the maven build just in the eclipse classpath. The > problem is that the property has a default value and by that deacivates the > WTP classpath! > included a patch for the 2.5 release, including some renaming so it won't > happen again. > please release a 2.5.1 version with this 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: (MDEP-157) "Unpack xxxto yyy" space
"Unpack xxxto yyy" space Key: MDEP-157 URL: http://jira.codehaus.org/browse/MDEP-157 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Reporter: Frank Cornelis Assignee: Brian Fox Attachments: unpack-to-space.patch See attachment for a fix. -- 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: (MSITE-146) Version not printing in strapline
[ http://jira.codehaus.org/browse/MSITE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Pizey reopened MSITE-146: - Still no version printing in strap line. > Version not printing in strapline > - > > Key: MSITE-146 > URL: http://jira.codehaus.org/browse/MSITE-146 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 > Environment: linux and XP >Reporter: Tim Pizey >Assignee: Dennis Lundberg > > The maven-site.vm has a missing #else, such that the publishDate macro fails > to print the version. > #if ( $version ) > #if ( $version.position ) > #set ( $versionPosition = $version.position ) > #else > #set ( $versionPosition = "left" ) > #end > #end > could become: > #if ( $version ) > #if ( $version.position ) > #set ( $versionPosition = $version.position ) > #else > #set ( $versionPosition = "left" ) > #end > #else > #set ( $version = "unset version" ) > #set ( $versionPosition = "left" ) > #end > which fixes for me. -- 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: (MSITE-147) Date format defaults to US
[ http://jira.codehaus.org/browse/MSITE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Pizey reopened MSITE-147: - Fix still has not hit the streets. > Date format defaults to US > --- > > Key: MSITE-147 > URL: http://jira.codehaus.org/browse/MSITE-147 > Project: Maven 2.x Site Plugin > Issue Type: Improvement >Affects Versions: 2.0-beta-4, 2.0-beta-5 > Environment: All >Reporter: Tim Pizey >Assignee: Dennis Lundberg >Priority: Trivial > Fix For: 2.0-beta-6 > > > Date format in maven-site.vm defaults to US format, not international, > suggest dd-MMM-yy -- 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: (MPMD-67) Using JDK 1.6 causes ParseException: Can't use generics unless running in JDK 1.5 mode!
[ http://jira.codehaus.org/browse/MPMD-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128875#action_128875 ] Tonte Pouncil commented on MPMD-67: --- I am experiencing the same issue as described above. This issue still exist for me, regardless if I use version 2.3 or 2.3-SNAPSHOT. Can someone else please verify this is really resolved? Are there any constraints or limitation when using this plugin? Thanks! > Using JDK 1.6 causes ParseException: Can't use generics unless running in JDK > 1.5 mode! > --- > > Key: MPMD-67 > URL: http://jira.codehaus.org/browse/MPMD-67 > Project: Maven 2.x PMD Plugin > Issue Type: Bug > Components: PMD >Affects Versions: 2.2 > Environment: Maven 2.0.8 > JDK 1.6 >Reporter: Will Hoover > Fix For: 2.3 > > > While using Maven PMD plugin with: > > org.apache.maven.plugins > maven-pmd-plugin > 2.2 > > true > utf-8 > 100 > > 1.6 > > > > **/generated/*.java > > > > I get the following error even though JDK is 1.6: > [WARNING] Failure executing PMD for: SomeGenericJavaClass.java > net.sourceforge.pmd.PMDException: Error while parsing > SomeGenericJavaClass.java > at net.sourceforge.pmd.PMD.processFile(PMD.java:104) > at net.sourceforge.pmd.PMD.processFile(PMD.java:64) > at net.sourceforge.pmd.PMD.processFile(PMD.java:150) > at > org.apache.maven.plugin.pmd.PmdReport.executeReport(PmdReport.java:228) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > 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:333) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) > 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: net.sourceforge.pmd.ast.ParseException: Can't use generics unless > running in JDK 1.5 mode! > at > net.sourceforge.pmd.ast.JavaParser.checkForBadGenericsUsage(JavaParser.java:32) > at > net.sourceforge.pmd.ast.JavaParser.TypeArguments(JavaParser.java:1962) > at > net.sourceforge.pmd.ast.JavaParser.ClassOrInterfaceType(JavaParser.java:1911) > at > net.sourceforge.pmd.ast.JavaParser.ReferenceType(JavaParser.java:1862) > at net.so
[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-tabpanel&focusedCommentId=128878#action_128878
]
Nils Eckert commented on MNG-3242:
--
I tried both.
Using a once escaped {{&}}-sign
{code:xml}
jdbc:mysql://localhost/mydb?user=myuser&password=mypass&useUnicode=true&characterEncoding=utf-8
{code}
I get the following error:
{code}
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot read project model
from interpolating filter of serialized version.
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
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: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)
Caused by: org.apache.maven.project.InvalidProjectModelException: Cannot read
project model from interpolating filter of serialized version.
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:812)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:479)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:537)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:364)
... 11 more
Caused by: org.apache.maven.project.interpolation.ModelInterpolationException:
Cannot read project model from interpolating filter of serialized version.
at
org.apache.maven.project.interpolation.RegexBasedModelInterpolator.interpolate(RegexBasedModelInterpolator.java:114)
at
org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:946)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:808)
... 16 more
Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: entity
reference name can not contain character =' (position: START_TAG seen
...c:mysql://localhost/nefo?createDatabaseIfNotExist=true&useUnicode=...
@133:85)
at
org.codehaus.plexus.util.xml.pull.MXParser.parseEntityRef(MXParser.java:2219)
at
org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1272)
at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1090)
at
hidden.org.codehaus.plexus.util.xml.Xpp3DomBuilder.build(Xpp3DomBuilder.java:187)
at
hidden.org.codehaus.plexus.util.xml.Xpp3DomBuilder.build(Xpp3DomBuilder.java:94)
at
org.apache.maven.model.io.xpp3.MavenXpp3Reader.parsePlugin(MavenXpp3Reader.java:2971)
at
org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseBuild(MavenXpp3Reader.java:769)
at
org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:2240)
at
org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:4438)
at
org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:4449)
at
org.apache.maven.project.interpolation.RegexBasedModelInterpolator.interpolate(RegexBasedModelInterpolator.java:105)
... 18 more
{code}
Using
{code}{code}
is working. But the filtered properties file containts {{&}} instead
of the expected {{&}}-sign.
If I'm using CDATA and do not escape the {{&}} sign, I'm getting an error
similar to the first one.
{code}{code}
For me it seems that there is no way to get an unescaped {{&}}-sign into a
properties-file.
> 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
>
>
> 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 f
[jira] Commented: (MSITE-229) Links in site.xml get translated to ../../../
[
http://jira.codehaus.org/browse/MSITE-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128879#action_128879
]
Mike Hanafey commented on MSITE-229:
I ran into the "URLs containing uninterpolated ${}" digression in John's
comment 2 hops above. In my case it was a failure to expand a property defined
in settings.xml, and in this case it is not clear why this expansion is not
done when the child site is generated by itself. Before reading this I had
opened [http://jira.codehaus.org/browse/MSITE-310].
Now I see it is a known issue, but it does seem like a reasonable idea to put
the deployment location in settings.xml, and there should be no issue with the
context this property needs to be resolved from.
> Links in site.xml get translated to ../../../
> -
>
> Key: MSITE-229
> URL: http://jira.codehaus.org/browse/MSITE-229
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: relative links
>Affects Versions: 2.0-beta-5
> Environment: Linux FC6 Sun Java (build 1.5.0_10-b03, mixed mode,
> sharing)
>Reporter: Mykel Alvis
>Assignee: Dennis Lundberg
>Priority: Minor
> Attachments: site.xml
>
>
> In Site.xml for a project (that has a parent POM)
>
> http://sirdsite.dsths.ad.dstcorp.net/"; />
> http://www.apache.org/"; />
> http://maven.apache.org/maven2/"/>
>
> Gets rendered as
>
> SIRD Site
> |
> http://www.apache.org/";>Apache
> |
> http://maven.apache.org/maven2/";>Maven 2
>
> " http://sirdsite.dsths.ad.dstcorp.net/"; != "../../.."
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (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-tabpanel&focusedCommentId=128881#action_128881
]
Nils Eckert commented on MNG-3242:
--
While I created a small sample pom to let you reproduce this behavior I noticed
to following. (See attached ZIP File: mvntest-20080327.zip)
The problem seems to be the reference of the {{dbunit-maven-plugin}} to my
jdbc.url property. If I remove this reference the compile and filtering works
as expected.
Is there something wrong with my configuration?
PS: I removed unnecessary configurations from that plugin to keep the pom as
small as possible.
> 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 & 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 &. Here I get a &
> 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 & 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] Updated: (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:all-tabpanel ] Nils Eckert updated MNG-3242: - Attachment: mvntest-20080327.zip Sample maven2 project for reproducing the behaviour. > 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 & 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 &. Here I get a & > 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 & 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: (MECLIPSE-413) EclipseOSGiManifestWriter uses the artifact id and not the EclipseProjectName
EclipseOSGiManifestWriter uses the artifact id and not the EclipseProjectName - Key: MECLIPSE-413 URL: http://jira.codehaus.org/browse/MECLIPSE-413 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: OSGi, Manifest Affects Versions: 2.5 Reporter: Richard van Nieuwenhoven Attachments: osgi.patch EclipseOSGiManifestWriter uses the artifact id and not the EclipseProjectName the EclipseOSGiManifestWriter should also honor the project name template! this is a very small 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: (SUREFIRE-479) @BeforeClass and @AfterClass on parent class are not executed
@BeforeClass and @AfterClass on parent class are not executed
-
Key: SUREFIRE-479
URL: http://jira.codehaus.org/browse/SUREFIRE-479
Project: Maven Surefire
Issue Type: Bug
Components: TestNG support
Affects Versions: 2.4.2
Reporter: Erik Putrycz
I have
public abstract class A {
@BeforeClass
public void init() {...}
@AfterClass
public void cleanup() {...}
}
and
@Test
public class TestA extends A {
public void testSomething() {...}
}
when surefire executes testSomething, the @BeforeClass and @AfterClass are
never being called. I have testng 5.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: (MECLIPSE-413) EclipseOSGiManifestWriter uses the artifact id and not the EclipseProjectName
[ http://jira.codehaus.org/browse/MECLIPSE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MECLIPSE-413. Resolution: Fixed Fix Version/s: 2.5.1 Patch applied in 2.5.1-20080327.151854-2 > EclipseOSGiManifestWriter uses the artifact id and not the EclipseProjectName > - > > Key: MECLIPSE-413 > URL: http://jira.codehaus.org/browse/MECLIPSE-413 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: OSGi, Manifest >Affects Versions: 2.5 >Reporter: Richard van Nieuwenhoven > Fix For: 2.5.1 > > Attachments: osgi.patch > > > EclipseOSGiManifestWriter uses the artifact id and not the EclipseProjectName > the EclipseOSGiManifestWriter should also honor the project name template! > this is a very small 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] 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-tabpanel&focusedCommentId=12#action_12 ] Nils Eckert commented on MNG-3242: -- I did some testings and the problem seems to be that the value is referenced. It is not a special problem of dbunit. > 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 & 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 &. Here I get a & > 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 & 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: (MDEPLOY-74) Add an option to be able to abort if an artifact is already present in the deployment repository
Add an option to be able to abort if an artifact is already present in the deployment repository Key: MDEPLOY-74 URL: http://jira.codehaus.org/browse/MDEPLOY-74 Project: Maven 2.x Deploy Plugin Issue Type: Improvement Reporter: Baptiste MATHUS Priority: Minor Hi all, Would be great if it was possible to use a command like: mvn deploy -DfailIfPresent=true (false by default, to behave as currently) That switch would do a build failure if the artifact is found in the deployment repository. Alternatively or in addition, a -DdryRun=true could add a simulation mode to this plugin. Particularly, it would clearly display if the artifact would be overriding an already present one or not. Cheers. -- 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: (MDEPLOY-74) Add an option to be able to abort if an artifact is already present in the deployment repository
[ http://jira.codehaus.org/browse/MDEPLOY-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128890#action_128890 ] Olivier Lamy commented on MDEPLOY-74: - IMHO, the parameter failIfPresent should be true by default. I know this won't preserve backward comp but it's will be a more "clean" process. > Add an option to be able to abort if an artifact is already present in the > deployment repository > > > Key: MDEPLOY-74 > URL: http://jira.codehaus.org/browse/MDEPLOY-74 > Project: Maven 2.x Deploy Plugin > Issue Type: Improvement >Reporter: Baptiste MATHUS >Priority: Minor > > Hi all, > Would be great if it was possible to use a command like: > mvn deploy -DfailIfPresent=true (false by default, to behave as currently) > That switch would do a build failure if the artifact is found in the > deployment repository. > Alternatively or in addition, a -DdryRun=true could add a simulation mode to > this plugin. Particularly, it would clearly display if the artifact would be > overriding an already present one or not. > Cheers. -- 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-311) NPE on absolute URLs if project.url not defined
NPE on absolute URLs if project.url not defined --- Key: MSITE-311 URL: http://jira.codehaus.org/browse/MSITE-311 Project: Maven 2.x Site Plugin Issue Type: Bug Components: relative links Affects Versions: 2.0-beta-7 Environment: JDK 1.5.0_13 on OS/X 10.5.2 Reporter: Brian Hanafee Priority: Critical Attachments: example.zip If there is no project url specified in the POM and there is a parent site.xml, then NPE on any absolute URLs found in the site.xml. Seems to work fine if there is no parent site.xml. java.lang.NullPointerException at org.apache.maven.doxia.site.decoration.inheritance.PathUtils.getRelativePath(PathUtils.java:83) at org.apache.maven.doxia.site.decoration.inheritance.PathUtils.convertPath(PathUtils.java:43) at org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.convertPath(DefaultDecorationModelInheritanceAssembler.java:334) at org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.resolveLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:255) at org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.resolveMenuPaths(DefaultDecorationModelInheritanceAssembler.java:246) at org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeMenus(DefaultDecorationModelInheritanceAssembler.java:228) at org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:203) at org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:83) at org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:1178) at org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:521) at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:226) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) 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: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) -- 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: (MDEPLOY-74) Add an option to be able to abort if an artifact is already present in the deployment repository
[ http://jira.codehaus.org/browse/MDEPLOY-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128891#action_128891 ] Benjamin Bentmann commented on MDEPLOY-74: -- bq. IMHO, the parameter failIfPresent should be true by default. +1 for regular releases, -1 for snapshots ;-) > Add an option to be able to abort if an artifact is already present in the > deployment repository > > > Key: MDEPLOY-74 > URL: http://jira.codehaus.org/browse/MDEPLOY-74 > Project: Maven 2.x Deploy Plugin > Issue Type: Improvement >Reporter: Baptiste MATHUS >Priority: Minor > > Hi all, > Would be great if it was possible to use a command like: > mvn deploy -DfailIfPresent=true (false by default, to behave as currently) > That switch would do a build failure if the artifact is found in the > deployment repository. > Alternatively or in addition, a -DdryRun=true could add a simulation mode to > this plugin. Particularly, it would clearly display if the artifact would be > overriding an already present one or not. > Cheers. -- 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-312) Interpolation not working in inherited elements
Interpolation not working in inherited elements --- Key: MSITE-312 URL: http://jira.codehaus.org/browse/MSITE-312 Project: Maven 2.x Site Plugin Issue Type: Bug Components: inheritance Affects Versions: 2.0-beta-7 Environment: JDK 1.5.0_13 on OS/X 10.5.2 Reporter: Brian Hanafee Attachments: example.zip Properties defined in the local POM are not interpolated into elements of the site that are inherited. In the attached example, the property "parentprop" is defined in the parent POM and "childprop" is defined in the child POM. The parent project has a site.xml that defines an inherited menu with items that reference both properties. Only parentprop is interpolated. The child project has an identical menu and the properties are interpolated correctly. -- 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: (MDEPLOY-74) Add an option to be able to abort if an artifact is already present in the deployment repository
[ http://jira.codehaus.org/browse/MDEPLOY-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128893#action_128893 ] Baptiste MATHUS commented on MDEPLOY-74: bq. +1 for regular releases, -1 for snapshots Well, this is only a problem with -DuniqueVersion=false I guess. Since default behaviour will generate a timestamp suffix, so that wouldn't override existing artifact. But IMO, this isn't a real problem since SNAPSHOT are unstable by definition, so maybe overriding it should be monitored at all. Maybe an additional option for the additional option could be added to handle this, like -DalsoForSnapshots :-). > Add an option to be able to abort if an artifact is already present in the > deployment repository > > > Key: MDEPLOY-74 > URL: http://jira.codehaus.org/browse/MDEPLOY-74 > Project: Maven 2.x Deploy Plugin > Issue Type: Improvement >Reporter: Baptiste MATHUS >Priority: Minor > > Hi all, > Would be great if it was possible to use a command like: > mvn deploy -DfailIfPresent=true (false by default, to behave as currently) > That switch would do a build failure if the artifact is found in the > deployment repository. > Alternatively or in addition, a -DdryRun=true could add a simulation mode to > this plugin. Particularly, it would clearly display if the artifact would be > overriding an already present one or not. > Cheers. -- 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-413) EclipseOSGiManifestWriter uses the artifact id and not the EclipseProjectName
[ http://jira.codehaus.org/browse/MECLIPSE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128898#action_128898 ] Carlos Sanchez commented on MECLIPSE-413: - isnt EclipseOSGiManifestWriter deprecated in favor of the felix plugin anyway ? > EclipseOSGiManifestWriter uses the artifact id and not the EclipseProjectName > - > > Key: MECLIPSE-413 > URL: http://jira.codehaus.org/browse/MECLIPSE-413 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: OSGi, Manifest >Affects Versions: 2.5 >Reporter: Richard van Nieuwenhoven >Assignee: Arnaud Heritier > Fix For: 2.5.1 > > Attachments: osgi.patch > > > EclipseOSGiManifestWriter uses the artifact id and not the EclipseProjectName > the EclipseOSGiManifestWriter should also honor the project name template! > this is a very small 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: (MAVENUPLOAD-1986) iText 2.1.0 released
iText 2.1.0 released Key: MAVENUPLOAD-1986 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1986 Project: maven-upload-requests Issue Type: Task Reporter: Bruno Lowagie Hello, I released iText 2.1.0 today. You can find the change-log file here: http://www.1t3xt.com/about/history.php?branch=history.21&node=210 You can download the POM, the bundle and the separate parts in the bundle here: http://itext.ugent.be/library/maven/ best regards, Bruno Lowagie -- 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-3328) Allow multiple profile activation properties.
[ http://jira.codehaus.org/browse/MNG-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128914#action_128914 ] Elifarley Callado Coelho commented on MNG-3328: --- Maybe adding support for boolean operators would be nice. Here is an example: --- prop-1 prop-2 prop-3 prop-4 prop-5 prop-6 MacOS --- > Allow multiple profile activation properties. > - > > Key: MNG-3328 > URL: http://jira.codehaus.org/browse/MNG-3328 > Project: Maven 2 > Issue Type: Improvement > Components: Profiles >Affects Versions: 2.0.8 >Reporter: Paul Gier > > The pom model should be changed to allow multiple properties to activate a > profile. So the profile activation section could look something like this: > > > some-value > another-value > > > This would provide more flexibility in profile activation. -- 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: (MDEP-157) "Unpack xxxto yyy" space
[ http://jira.codehaus.org/browse/MDEP-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MDEP-157. -- Resolution: Fixed Fix Version/s: 2.1 Applied, thanks for the patch > "Unpack xxxto yyy" space > > > Key: MDEP-157 > URL: http://jira.codehaus.org/browse/MDEP-157 > Project: Maven 2.x Dependency Plugin > Issue Type: Improvement >Reporter: Frank Cornelis >Assignee: Brian Fox > Fix For: 2.1 > > Attachments: unpack-to-space.patch > > > See attachment for a fix. -- 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: (MDEP-139) Add missing whitespace in log message "Unpacking to"
[
http://jira.codehaus.org/browse/MDEP-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox closed MDEP-139.
--
Resolution: Duplicate
patch from MDEP-157 applied
> Add missing whitespace in log message "Unpacking to"
> --
>
> Key: MDEP-139
> URL: http://jira.codehaus.org/browse/MDEP-139
> Project: Maven 2.x Dependency Plugin
> Issue Type: Task
> Components: unpack, unpack-dependencies
>Affects Versions: 2.0
>Reporter: Benjamin Bentmann
>Assignee: Brian Fox
>Priority: Trivial
> Attachments: unpack-logging.patch
>
>
> {noformat}
> [INFO] Unpacking
> snip\maven-dependency-plugin\target\unit-tests\unpack\localTestRepo\test-1.0.jarto
> snip\maven-dependency-plugin\target\unit-tests\unpack\outputDirectory
> with Includes null and excludes:**/*
> {noformat}
> could look nicer ;-)
--
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-413) EclipseOSGiManifestWriter uses the artifact id and not the EclipseProjectName
[ http://jira.codehaus.org/browse/MECLIPSE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128935#action_128935 ] Richard van Nieuwenhoven commented on MECLIPSE-413: --- true, but the necessary pde option destroys my manifest. An alternative would be to deactivate it, but that would be a big change for a 2.5.1 release. > EclipseOSGiManifestWriter uses the artifact id and not the EclipseProjectName > - > > Key: MECLIPSE-413 > URL: http://jira.codehaus.org/browse/MECLIPSE-413 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: OSGi, Manifest >Affects Versions: 2.5 >Reporter: Richard van Nieuwenhoven >Assignee: Arnaud Heritier > Fix For: 2.5.1 > > Attachments: osgi.patch > > > EclipseOSGiManifestWriter uses the artifact id and not the EclipseProjectName > the EclipseOSGiManifestWriter should also honor the project name template! > this is a very small 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] Commented: (MSITE-163) The modules menu is not inherited
[ http://jira.codehaus.org/browse/MSITE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128939#action_128939 ] Tonte Pouncil commented on MSITE-163: - I am having the same issue, too! My project is a flat Maven2 multiproject; so I am interested in knowing if the solution support flat Maven2 multiproject. Can someone verify this? Thanks! > 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-7 > > > if I have a site.xml in a parent project that contains the line ref="modules" inherit="top" /> it is not inherited by child projects. > 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] Commented: (MWAR-5) warSourceExcludes not working properly
[
http://jira.codehaus.org/browse/MWAR-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128940#action_128940
]
Daniel Uribe commented on MWAR-5:
-
I see that there seem to be some changes in the trunk that could be related to
this issue, is it planned for the next release of the plugin? It seems that the
2.1 alpha 1 doesn't have this fix yet, but since it's in the trunk, the next
alpha or beta might. Is there any timeframe for that release?
> warSourceExcludes not working properly
> --
>
> Key: MWAR-5
> URL: http://jira.codehaus.org/browse/MWAR-5
> Project: Maven 2.x War Plugin
> Issue Type: Bug
> Environment: Win2k, Java 1.4.2_04, m2 beta1
>Reporter: Fabrice BELLINGARD
>Assignee: Edwin Punzalan
> Fix For: 2.0
>
> Attachments: MNG-1038-maven-war-plugin.patch,
> MNG-1038-maven-war-plugin.patch
>
>
> Note: I posted a message on Maven users list
> (http://www.mail-archive.com/users%40maven.apache.org/msg24088.html), but I
> got no answer so I post this issue, which in turn may or not be a bug...
> (sorry if it's not)
> I experienced a strange behaviour with the 'warSourceExcludes' property. When
> I grab some Web projects from the CVS of my company, I usually get all the
> WEB-INF/lib Jars that the developers put in the CVS:
> - With Maven 1, I use the 'maven.war.src.excludes' property to exclude those
> Jars ('maven.war.src.excludes=**/lib/*.*'), and it works well: the Jars
> packaged in the War are only the ones defined in the pom.
> - With m2, I tried to use the 'warSourceExcludes' property, which seemed to
> me to be the equivalent property. However, when the War is generated, there
> is no jar in the WEB-INF/lib folder. This works as if the plugin is excluding
> files after having copied the needed dependencies in the WEB-INF/lib folder
> (whereas in the Maven 1 version, it was excluding them before).
> Looking at the code of the m2 plugin, the value of 'warSourceExcludes' is
> used in method #getExcludes which is actually called in #performPackaging
> method. If this property is to work the same way as in m1, its value should
> be used in #copyResources method, before copying the Jar dependencies in
> WEB-INF/lib.
> What do you guys think of that? Am I right or am I missing something?
--
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-146) Version not printing in strapline
[ http://jira.codehaus.org/browse/MSITE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-146: -- Attachment: MSITE-146.zip Here is a minimal project that in fact proves that it *does* work. It also proves that MSITE-147 works. > Version not printing in strapline > - > > Key: MSITE-146 > URL: http://jira.codehaus.org/browse/MSITE-146 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 > Environment: linux and XP >Reporter: Tim Pizey >Assignee: Dennis Lundberg > Attachments: MSITE-146.zip > > > The maven-site.vm has a missing #else, such that the publishDate macro fails > to print the version. > #if ( $version ) > #if ( $version.position ) > #set ( $versionPosition = $version.position ) > #else > #set ( $versionPosition = "left" ) > #end > #end > could become: > #if ( $version ) > #if ( $version.position ) > #set ( $versionPosition = $version.position ) > #else > #set ( $versionPosition = "left" ) > #end > #else > #set ( $version = "unset version" ) > #set ( $versionPosition = "left" ) > #end > which fixes for me. -- 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-146) Version not printing in strapline
[ http://jira.codehaus.org/browse/MSITE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-146. - Resolution: Won't Fix > Version not printing in strapline > - > > Key: MSITE-146 > URL: http://jira.codehaus.org/browse/MSITE-146 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 > Environment: linux and XP >Reporter: Tim Pizey >Assignee: Dennis Lundberg > Attachments: MSITE-146.zip > > > The maven-site.vm has a missing #else, such that the publishDate macro fails > to print the version. > #if ( $version ) > #if ( $version.position ) > #set ( $versionPosition = $version.position ) > #else > #set ( $versionPosition = "left" ) > #end > #end > could become: > #if ( $version ) > #if ( $version.position ) > #set ( $versionPosition = $version.position ) > #else > #set ( $versionPosition = "left" ) > #end > #else > #set ( $version = "unset version" ) > #set ( $versionPosition = "left" ) > #end > which fixes for me. -- 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-147) Date format defaults to US
[ http://jira.codehaus.org/browse/MSITE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-147. - Resolution: Fixed See my test project in MSITE-146. > Date format defaults to US > --- > > Key: MSITE-147 > URL: http://jira.codehaus.org/browse/MSITE-147 > Project: Maven 2.x Site Plugin > Issue Type: Improvement >Affects Versions: 2.0-beta-4, 2.0-beta-5 > Environment: All >Reporter: Tim Pizey >Assignee: Dennis Lundberg >Priority: Trivial > Fix For: 2.0-beta-6 > > > Date format in maven-site.vm defaults to US format, not international, > suggest dd-MMM-yy -- 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-1987) Please sync net.sourceforge.cssparser
Please sync net.sourceforge.cssparser - Key: MAVENUPLOAD-1987 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1987 Project: maven-upload-requests Issue Type: Wish Reporter: Daniel Gredler "net.sourceforge.cssparser","[EMAIL PROTECTED]:/home/groups/c/cs/cssparser/htdocs/m2-repo","rsync_ssh","Daniel Gredler","[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: (MAVENUPLOAD-1988) Please sync with net.sf.jopt-simple automatically
Please sync with net.sf.jopt-simple automatically - Key: MAVENUPLOAD-1988 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1988 Project: maven-upload-requests Issue Type: Task Reporter: Paul Holser "net.sf.jopt-simple","[EMAIL PROTECTED]:/home/groups/j/jo/jopt-simple/htdocs/maven","rsync_ssh","Paul Holser","[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: (MPATCH-3) Path with space make command line invocation fail
Path with space make command line invocation fail - Key: MPATCH-3 URL: http://jira.codehaus.org/browse/MPATCH-3 Project: Maven 2.x Patch Plugin Issue Type: Bug Affects Versions: 1.0 Reporter: Benjamin Bentmann Priority: Critical Attachments: build.log The old story... -- 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-412) Generation of jst.java Facet for EAR packaging kills my RAD workspace
[ http://jira.codehaus.org/browse/MECLIPSE-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MECLIPSE-412. Resolution: Duplicate Fixed in maven-eclipse-plugin 2.5.1-20080327.221549-3 > Generation of jst.java Facet for EAR packaging kills my RAD workspace > - > > Key: MECLIPSE-412 > URL: http://jira.codehaus.org/browse/MECLIPSE-412 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: RAD support, WTP support >Affects Versions: 2.5 > Environment: Windows, RAD 7.0.0.5 >Reporter: Kuno Baeriswyl >Assignee: Arnaud Heritier > Fix For: 2.5.1 > > Attachments: EclipseWtpFacetsWriter-RAD-patch.txt > > > The eclipse:eclipse or eclipse:rad goals generate jst.java Facets like : > > > > > > > > > > This facets aren't necessary for EAR artifacts in RAD, brings it in a strange > state and kills my workspace. The side effects are particularly annoying in > the debug mode, where on every step an error message pop-ups. The > maven-eclipse-plugin must avoid this facets and generate them like following: > > > > > > > > I think you have done a great work with the recent 2.5 release. Just need to > have fixed this. Thanks for everything. -- 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-266) plugin applies java facet to ear project
[ http://jira.codehaus.org/browse/MECLIPSE-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MECLIPSE-266. Resolution: Fixed Patch applied in maven-eclipse-plugin 2.5.1-20080327.221549-3. Thx. > plugin applies java facet to ear project > > > Key: MECLIPSE-266 > URL: http://jira.codehaus.org/browse/MECLIPSE-266 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.3 > Environment: Windows XP >Reporter: Srepfler Srgjan >Assignee: Arnaud Heritier > Fix For: 2.5.1 > > Attachments: MECLIPSE-266-2.5.patch, > MECLIPSE-266-maven-eclipse-plugin.patch, MECLIPSE-266.patch > > > In .settings/org.eclipse.wst.common.project.facet.core.xml of the EAR module > I'm getting this: > > > > > > > This is a wrong facet on a EAR module and I can't compile if I don't edit > this file manually (I can't do it from the project properties - facets dialog) -- 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: (MPATCH-3) Path with space make command line invocation fail
[ http://jira.codehaus.org/browse/MPATCH-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MPATCH-3. -- Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 1.1 Fixed in [r642018|http://svn.apache.org/viewvc?view=rev&revision=642018]. > Path with space make command line invocation fail > - > > Key: MPATCH-3 > URL: http://jira.codehaus.org/browse/MPATCH-3 > Project: Maven 2.x Patch Plugin > Issue Type: Bug >Affects Versions: 1.0 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann >Priority: Critical > Fix For: 1.1 > > Attachments: build.log > > > The old story... -- 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: (MPATCH-1) Support deletion of empty files after the patches have been applied
[ http://jira.codehaus.org/browse/MPATCH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MPATCH-1. -- Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 1.1 Applied in [r642023|http://svn.apache.org/viewvc?view=rev&revision=642023], thanks! > Support deletion of empty files after the patches have been applied > --- > > Key: MPATCH-1 > URL: http://jira.codehaus.org/browse/MPATCH-1 > Project: Maven 2.x Patch Plugin > Issue Type: New Feature >Affects Versions: 1.0 >Reporter: Napoleon Esmundo C. Ramirez >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 1.1 > > Attachments: MPATCH-1.patch > > > By default, the patch command does not delete empty files after the patches > have been applied. Compilation breaks on empty java sources. According to > the man pages, as a workaround, the to be deleted could be compared to an > empty file dated the Epoch (1970-01-01 00:00:00 UTC) if it conforms to POSIX. > Or better yet, use the -E or --remove-empty-files option to be sure. -- 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: (MDEPLOY-57) false not honored inside
[ http://jira.codehaus.org/browse/MDEPLOY-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128965#action_128965 ] programr edited comment on MDEPLOY-57 at 3/27/08 6:58 PM: Guys, if I can even get some tips on how to fix this, I will do my best to do the coding myself. I need this fixed desperately, but need some pointers on getting started with a fix... My area of code familiarity is not the deploy plugin. This still occurs with Maven 2.0.8 and the latest dependencies in the central repo. was (Author: programr): Guys, if I can even get some tips on how to fix this, I will do my best to do the coding myself. I need this fixed desperately, but need some pointers on getting started with a fix... My area of code familiarity is not the deploy plugin. > false not honored inside > - > > Key: MDEPLOY-57 > URL: http://jira.codehaus.org/browse/MDEPLOY-57 > Project: Maven 2.x Deploy Plugin > Issue Type: Bug >Affects Versions: 2.3 > Environment: Windows XP SP2 > Maven 2.0.7 > Java 6 U1 >Reporter: Matthew McCullough >Priority: Critical > Attachments: effectivepom2.txt, pom.xml > > > I am invoking maven as: > mvn deploy -DCCDistribution > The appropriate section of my pom.xml is below. > In the attachment, I've provided the redirected output of "mvn > help:effective-pom -DCCDistribution". > And lastly, I've provided a snippet of build console output. > - SECTION OF POMNOT BEING HONORED > > > CCDistribution > > > CCDistribution > > > > > KenanFX_M2_Repo > KenanFX Maven 2 Repository > ftp://maven.kenan.com/KenanFX/m2_repo > false > > > > CONSOLE OUTPUT SNIPPET SHOWING UNIQUE DATESTAMPED VERSIONS, > THOUGH NONUNIQUE ARE DESIRED > > [INFO] > > [INFO] Building CCBS UDT Functional API > [INFO]task-segment: [deploy] > [INFO] > > [INFO] [site:attach-descriptor] > [INFO] [install:install] > [INFO] Installing c:\ClearCaseSource\mccm03_view3\single_api_src\udt\pom.xml > to C:\Documents and Settings\mccm03\.m2\repository\com\comverse\api\udt\c > cbs-udt\1.0.M1-SNAPSHOT\ccbs-udt-1.0.M1-SNAPSHOT.pom > [INFO] [deploy:deploy] > altDeploymentRepository = null > [INFO] Retrieving previous build number from KenanFX_M2_Repo > Uploading: > ftp://maven.kenan.com/KenanFX/m2_repo/com/comverse/api/udt/ccbs-udt/1.0.M1-SNAPSHOT/ccbs-udt-1.0.M1-SNAPSHOT.pom > 721b uploaded > [INFO] Retrieving previous metadata from KenanFX_M2_Repo > [INFO] Uploading repository metadata for: 'artifact > com.comverse.api.udt:ccbs-udt' > [INFO] Retrieving previous metadata from KenanFX_M2_Repo > [INFO] Uploading repository metadata for: 'snapshot > com.comverse.api.udt:ccbs-udt:1.0.M1-SNAPSHOT' > [INFO] > > [INFO] Building CCBS UDT Shared > [INFO]task-segment: [deploy] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:compile] > [INFO] Nothing to compile - all classes are up to date > [INFO] [resources:testResources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:testCompile] > [INFO] Not compiling test sources > [INFO] [surefire:test] > [INFO] Tests are skipped. > [INFO] [jar:jar] > [INFO] Building jar: > C:\ClearCaseSource\mccm03_view3\single_api_src\udt\shared\target\ccbs-udt-shared-1.0.M1-SNAPSHOT.jar > [INFO] [install:install] > [INFO] Installing > C:\ClearCaseSource\mccm03_view3\single_api_src\udt\shared\target\ccbs-udt-shared-1.0.M1-SNAPSHOT.jar > to C:\Documents and Settings\mc > cm03\.m2\repository\com\comverse\api\udt\ccbs-udt-shared\1.0.M1-SNAPSHOT\ccbs-udt-shared-1.0.M1-SNAPSHOT.jar > [INFO] [deploy:deploy] > altDeploymentRepository = null > [INFO] Retrieving previous build number from KenanFX_M2_Repo > Uploading: > ftp://maven.kenan.com/KenanFX/m2_repo/com/comverse/api/udt/ccbs-udt-shared/1.0.M1-SNAPSHOT/ccbs-udt-shared-1.0.M1-20070718.004617-1.jar > 6K uploaded > [INFO] Retrieving previous metadata from KenanFX_M2_Repo > [INFO] Uploading repository metadata for: 'artifact > com.comverse.api.udt:ccbs-udt-shared' > [INFO] Retrieving previous metadata from KenanFX_M2_Repo > [INFO] Uploading repository metadata for: 'snapshot > com.comverse.api.udt:ccbs-udt-shared:1.0.M1-SNAPSHOT' > [INFO] Retrieving previous metadata from KenanFX_M2_Repo -- This message
[jira] Commented: (MDEPLOY-57) false not honored inside
[ http://jira.codehaus.org/browse/MDEPLOY-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128965#action_128965 ] Matthew McCullough commented on MDEPLOY-57: --- Guys, if I can even get some tips on how to fix this, I will do my best to do the coding myself. I need this fixed desperately, but need some pointers on getting started with a fix... My area of code familiarity is not the deploy plugin. > false not honored inside > - > > Key: MDEPLOY-57 > URL: http://jira.codehaus.org/browse/MDEPLOY-57 > Project: Maven 2.x Deploy Plugin > Issue Type: Bug >Affects Versions: 2.3 > Environment: Windows XP SP2 > Maven 2.0.7 > Java 6 U1 >Reporter: Matthew McCullough >Priority: Critical > Attachments: effectivepom2.txt, pom.xml > > > I am invoking maven as: > mvn deploy -DCCDistribution > The appropriate section of my pom.xml is below. > In the attachment, I've provided the redirected output of "mvn > help:effective-pom -DCCDistribution". > And lastly, I've provided a snippet of build console output. > - SECTION OF POMNOT BEING HONORED > > > CCDistribution > > > CCDistribution > > > > > KenanFX_M2_Repo > KenanFX Maven 2 Repository > ftp://maven.kenan.com/KenanFX/m2_repo > false > > > > CONSOLE OUTPUT SNIPPET SHOWING UNIQUE DATESTAMPED VERSIONS, > THOUGH NONUNIQUE ARE DESIRED > > [INFO] > > [INFO] Building CCBS UDT Functional API > [INFO]task-segment: [deploy] > [INFO] > > [INFO] [site:attach-descriptor] > [INFO] [install:install] > [INFO] Installing c:\ClearCaseSource\mccm03_view3\single_api_src\udt\pom.xml > to C:\Documents and Settings\mccm03\.m2\repository\com\comverse\api\udt\c > cbs-udt\1.0.M1-SNAPSHOT\ccbs-udt-1.0.M1-SNAPSHOT.pom > [INFO] [deploy:deploy] > altDeploymentRepository = null > [INFO] Retrieving previous build number from KenanFX_M2_Repo > Uploading: > ftp://maven.kenan.com/KenanFX/m2_repo/com/comverse/api/udt/ccbs-udt/1.0.M1-SNAPSHOT/ccbs-udt-1.0.M1-SNAPSHOT.pom > 721b uploaded > [INFO] Retrieving previous metadata from KenanFX_M2_Repo > [INFO] Uploading repository metadata for: 'artifact > com.comverse.api.udt:ccbs-udt' > [INFO] Retrieving previous metadata from KenanFX_M2_Repo > [INFO] Uploading repository metadata for: 'snapshot > com.comverse.api.udt:ccbs-udt:1.0.M1-SNAPSHOT' > [INFO] > > [INFO] Building CCBS UDT Shared > [INFO]task-segment: [deploy] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:compile] > [INFO] Nothing to compile - all classes are up to date > [INFO] [resources:testResources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:testCompile] > [INFO] Not compiling test sources > [INFO] [surefire:test] > [INFO] Tests are skipped. > [INFO] [jar:jar] > [INFO] Building jar: > C:\ClearCaseSource\mccm03_view3\single_api_src\udt\shared\target\ccbs-udt-shared-1.0.M1-SNAPSHOT.jar > [INFO] [install:install] > [INFO] Installing > C:\ClearCaseSource\mccm03_view3\single_api_src\udt\shared\target\ccbs-udt-shared-1.0.M1-SNAPSHOT.jar > to C:\Documents and Settings\mc > cm03\.m2\repository\com\comverse\api\udt\ccbs-udt-shared\1.0.M1-SNAPSHOT\ccbs-udt-shared-1.0.M1-SNAPSHOT.jar > [INFO] [deploy:deploy] > altDeploymentRepository = null > [INFO] Retrieving previous build number from KenanFX_M2_Repo > Uploading: > ftp://maven.kenan.com/KenanFX/m2_repo/com/comverse/api/udt/ccbs-udt-shared/1.0.M1-SNAPSHOT/ccbs-udt-shared-1.0.M1-20070718.004617-1.jar > 6K uploaded > [INFO] Retrieving previous metadata from KenanFX_M2_Repo > [INFO] Uploading repository metadata for: 'artifact > com.comverse.api.udt:ccbs-udt-shared' > [INFO] Retrieving previous metadata from KenanFX_M2_Repo > [INFO] Uploading repository metadata for: 'snapshot > com.comverse.api.udt:ccbs-udt-shared:1.0.M1-SNAPSHOT' > [INFO] Retrieving previous metadata from KenanFX_M2_Repo -- 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: (SUREFIRE-459) Integration test using Jetty and JSP 2.1 fails after update to maven-surefire-plugin 2.4
[ http://jira.codehaus.org/browse/SUREFIRE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich reopened SUREFIRE-459: --- Assignee: Dan Fabulich We just found a repro case for this at Redfin. I'll attach a sample that repro's the problem. > Integration test using Jetty and JSP 2.1 fails after update to > maven-surefire-plugin 2.4 > > > Key: SUREFIRE-459 > URL: http://jira.codehaus.org/browse/SUREFIRE-459 > Project: Maven Surefire > Issue Type: Bug > Components: classloading, plugin >Affects Versions: 2.4, 2.4.1 > Environment: Maven 2.0.8, Windows XP >Reporter: Nils-Helge Garli >Assignee: Dan Fabulich > > We have an integration test running in a Struts 2 sample application, and > after the maven-surefire-plugin was updated from 2.3 to 2.4, the test is > failing. There's an issue registered in the Struts 2 JIRA explaining the > error: https://issues.apache.org/struts/browse/WW-2494 > I have no idea what's causing the error, but I suspect it has something to do > witn classloader configuration, as aparently no tld files are found inside > the jar files on the classpath. > It should be pretty easy to reproduce. Just checkout the Struts 2 code and > run 'mvn test' on the portlet example application. -- 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: (MDEPLOY-57) false not honored inside
[ http://jira.codehaus.org/browse/MDEPLOY-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128969#action_128969 ] Benjamin Bentmann commented on MDEPLOY-57: -- bq. Guys, if I can even get some tips on how to fix this, I will do my best to do the coding myself. Here's the source code for the Deploy Plugin: https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-deploy-plugin Check it out and setup the Maven project in your IDE with source attachments. You could then start coding and remote debugging your changes. > false not honored inside > - > > Key: MDEPLOY-57 > URL: http://jira.codehaus.org/browse/MDEPLOY-57 > Project: Maven 2.x Deploy Plugin > Issue Type: Bug >Affects Versions: 2.3 > Environment: Windows XP SP2 > Maven 2.0.7 > Java 6 U1 >Reporter: Matthew McCullough >Priority: Critical > Attachments: effectivepom2.txt, pom.xml > > > I am invoking maven as: > mvn deploy -DCCDistribution > The appropriate section of my pom.xml is below. > In the attachment, I've provided the redirected output of "mvn > help:effective-pom -DCCDistribution". > And lastly, I've provided a snippet of build console output. > - SECTION OF POMNOT BEING HONORED > > > CCDistribution > > > CCDistribution > > > > > KenanFX_M2_Repo > KenanFX Maven 2 Repository > ftp://maven.kenan.com/KenanFX/m2_repo > false > > > > CONSOLE OUTPUT SNIPPET SHOWING UNIQUE DATESTAMPED VERSIONS, > THOUGH NONUNIQUE ARE DESIRED > > [INFO] > > [INFO] Building CCBS UDT Functional API > [INFO]task-segment: [deploy] > [INFO] > > [INFO] [site:attach-descriptor] > [INFO] [install:install] > [INFO] Installing c:\ClearCaseSource\mccm03_view3\single_api_src\udt\pom.xml > to C:\Documents and Settings\mccm03\.m2\repository\com\comverse\api\udt\c > cbs-udt\1.0.M1-SNAPSHOT\ccbs-udt-1.0.M1-SNAPSHOT.pom > [INFO] [deploy:deploy] > altDeploymentRepository = null > [INFO] Retrieving previous build number from KenanFX_M2_Repo > Uploading: > ftp://maven.kenan.com/KenanFX/m2_repo/com/comverse/api/udt/ccbs-udt/1.0.M1-SNAPSHOT/ccbs-udt-1.0.M1-SNAPSHOT.pom > 721b uploaded > [INFO] Retrieving previous metadata from KenanFX_M2_Repo > [INFO] Uploading repository metadata for: 'artifact > com.comverse.api.udt:ccbs-udt' > [INFO] Retrieving previous metadata from KenanFX_M2_Repo > [INFO] Uploading repository metadata for: 'snapshot > com.comverse.api.udt:ccbs-udt:1.0.M1-SNAPSHOT' > [INFO] > > [INFO] Building CCBS UDT Shared > [INFO]task-segment: [deploy] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:compile] > [INFO] Nothing to compile - all classes are up to date > [INFO] [resources:testResources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:testCompile] > [INFO] Not compiling test sources > [INFO] [surefire:test] > [INFO] Tests are skipped. > [INFO] [jar:jar] > [INFO] Building jar: > C:\ClearCaseSource\mccm03_view3\single_api_src\udt\shared\target\ccbs-udt-shared-1.0.M1-SNAPSHOT.jar > [INFO] [install:install] > [INFO] Installing > C:\ClearCaseSource\mccm03_view3\single_api_src\udt\shared\target\ccbs-udt-shared-1.0.M1-SNAPSHOT.jar > to C:\Documents and Settings\mc > cm03\.m2\repository\com\comverse\api\udt\ccbs-udt-shared\1.0.M1-SNAPSHOT\ccbs-udt-shared-1.0.M1-SNAPSHOT.jar > [INFO] [deploy:deploy] > altDeploymentRepository = null > [INFO] Retrieving previous build number from KenanFX_M2_Repo > Uploading: > ftp://maven.kenan.com/KenanFX/m2_repo/com/comverse/api/udt/ccbs-udt-shared/1.0.M1-SNAPSHOT/ccbs-udt-shared-1.0.M1-20070718.004617-1.jar > 6K uploaded > [INFO] Retrieving previous metadata from KenanFX_M2_Repo > [INFO] Uploading repository metadata for: 'artifact > com.comverse.api.udt:ccbs-udt-shared' > [INFO] Retrieving previous metadata from KenanFX_M2_Repo > [INFO] Uploading repository metadata for: 'snapshot > com.comverse.api.udt:ccbs-udt-shared:1.0.M1-SNAPSHOT' > [INFO] Retrieving previous metadata from KenanFX_M2_Repo -- 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: (SUREFIRE-459) Integration test using Jetty and JSP 2.1 fails after update to maven-surefire-plugin 2.4
[ http://jira.codehaus.org/browse/SUREFIRE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-459. - Resolution: Fixed Fix Version/s: 2.5 Fixed in revision 642046. By default forkMode=once and useSystemclassloader=true, which causes us to launch the tests using a a manifest-only jar; this confuses Jetty when it uses the system property "java.class.path" to javac to compile JSPs. Fixed by deliberately "faking out" the java.class.path, setting it to what the classpath would have been if we'd launched the app in a conventional way. This also has the benefit of more generally insulating our users from the manifest-only jar; java.class.path will look "normal" now. In the short term, there is an easy workaround for this, which is to set useSystemClassLoader=false. (My initial guess was correct.) > Integration test using Jetty and JSP 2.1 fails after update to > maven-surefire-plugin 2.4 > > > Key: SUREFIRE-459 > URL: http://jira.codehaus.org/browse/SUREFIRE-459 > Project: Maven Surefire > Issue Type: Bug > Components: classloading, plugin >Affects Versions: 2.4, 2.4.1 > Environment: Maven 2.0.8, Windows XP >Reporter: Nils-Helge Garli >Assignee: Dan Fabulich > Fix For: 2.5 > > > We have an integration test running in a Struts 2 sample application, and > after the maven-surefire-plugin was updated from 2.3 to 2.4, the test is > failing. There's an issue registered in the Struts 2 JIRA explaining the > error: https://issues.apache.org/struts/browse/WW-2494 > I have no idea what's causing the error, but I suspect it has something to do > witn classloader configuration, as aparently no tld files are found inside > the jar files on the classpath. > It should be pretty easy to reproduce. Just checkout the Struts 2 code and > run 'mvn test' on the portlet example application. -- 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-103) Wagon Webdav does not handle HTTP redirects gracefully.
Wagon Webdav does not handle HTTP redirects gracefully. --- Key: WAGON-103 URL: http://jira.codehaus.org/browse/WAGON-103 Project: wagon Issue Type: Bug Components: wagon-webdav Affects Versions: 1.0-beta-2 Reporter: James William Dumay 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
