[jira] Reopened: (MPOM-7) Apache Parent Pom should be properly documented
[ https://issues.apache.org/jira/browse/MPOM-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reopened MPOM-7: - The POM still needs the dcoumentation. > Apache Parent Pom should be properly documented > --- > > Key: MPOM-7 > URL: https://issues.apache.org/jira/browse/MPOM-7 > Project: Maven POM > Issue Type: Improvement >Reporter: Sebb >Assignee: Olivier Lamy > Fix For: ASF-9 > > > There does not appear to be any documentation on the Apache Parent Pom. > Please can the following be added to the next release: > * how to report issues > * where to find the source > Ideally there should be a page on the Maven web-site that documents it as > well. > In which case please link to that from the POM as well. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-552) site.xml parameter and template variables not documented
site.xml parameter and template variables not documented - Key: MSITE-552 URL: http://jira.codehaus.org/browse/MSITE-552 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Reporter: SebbASF There's no proper documentation on the Maven site descriptor "custom" tag. It's not mentioned in the main documentation [1], and is only mentioned in passing in [2] - which in turn is not referenced from [1] Here are the full details from [2]: custom DOM Custom configuration for use with customized Velocity templates The DOM reference above appears to be an instance of Xpp3Dom [3]. Also, the Doxia code sets various context variables (in DefaultSiteRenderer ?). This should all be documented, along with some simple examples, and referenced as necessary from the Maven site plugin documentation [1] http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html [2] http://maven.apache.org/doxia/doxia-sitetools/doxia-decoration-model/decoration.html [3] http://plexus.codehaus.org/plexus-utils/apidocs/org/codehaus/plexus/util/xml/Xpp3Dom.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] Created: (MSITE-551) custom content not returned correctly
custom content not returned correctly
-
Key: MSITE-551
URL: http://jira.codehaus.org/browse/MSITE-551
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Reporter: SebbASF
Given the following:
{code:title=site.xml}
Content
{code}
and the template snippet:
{code:title=template.vm}
$decoration.custom
{code}
the output is:
{noformat}
Content
{noformat}
The first line should not be present.
--
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-550) site:site parameter does not work
site:site parameter does not work
--
Key: MSITE-550
URL: http://jira.codehaus.org/browse/MSITE-550
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Affects Versions: 2.2
Reporter: SebbASF
The site:site goal has an optional attributes parameter:
{quote}
attributes:
The template properties for rendering the site.
* Type: java.util.Map
* Required: No
* Expression: ${attributes}
{quote}
However this does not work - no parameters are created for the template.
--
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: (MPOM-1) apache-release does unwanted things in the prepare goal
[ https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993234#comment-12993234 ] Hudson commented on MPOM-1: --- Integrated in ASF Parent Pom #13 (See [https://hudson.apache.org/hudson/job/ASF%20Parent%20Pom/13/]) revert the site additions to the asf pom MPOM-1 MPOM-5 MPOM-7 > apache-release does unwanted things in the prepare goal > --- > > Key: MPOM-1 > URL: https://issues.apache.org/jira/browse/MPOM-1 > Project: Maven POM > Issue Type: Bug >Reporter: Olivier Lamy >Assignee: Brian Fox > Fix For: ASF-9 > > > Release 7 of the org.apache:apache use -P to turn on an 'apache-release' > profile in the release plugin. By using -P, this profile is turned on in > prepare as well as perform. > This may turn into a contest of opinion, and you all may just tell me to jump > in a lake, but I think this is a bad idea. At prepare time, we're just > looking to get the versions setup and the tag made. Having to deal with gpg > signing, and source archiving seems out of place. > At very least, I'd request that this the element be left out of > the release plugin spec. If some project wants to use that particular > collection of functions, fine. For the rest of us, who just want to get > distribution management and other universals, you we wouldn't have to worry > about it. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPOM-5) Produce documentation of this POM that can be added to the infra site.
[ https://issues.apache.org/jira/browse/MPOM-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993232#comment-12993232 ] Hudson commented on MPOM-5: --- Integrated in ASF Parent Pom #13 (See [https://hudson.apache.org/hudson/job/ASF%20Parent%20Pom/13/]) revert the site additions to the asf pom MPOM-1 MPOM-5 MPOM-7 > Produce documentation of this POM that can be added to the infra site. > -- > > Key: MPOM-5 > URL: https://issues.apache.org/jira/browse/MPOM-5 > Project: Maven POM > Issue Type: Improvement >Reporter: Benson Margulies >Assignee: Olivier Lamy > Fix For: ASF-9 > > Attachments: MPOM-5.patch > > > Patch coming right up. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPOM-7) Apache Parent Pom should be properly documented
[ https://issues.apache.org/jira/browse/MPOM-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993233#comment-12993233 ] Hudson commented on MPOM-7: --- Integrated in ASF Parent Pom #13 (See [https://hudson.apache.org/hudson/job/ASF%20Parent%20Pom/13/]) revert the site additions to the asf pom MPOM-1 MPOM-5 MPOM-7 > Apache Parent Pom should be properly documented > --- > > Key: MPOM-7 > URL: https://issues.apache.org/jira/browse/MPOM-7 > Project: Maven POM > Issue Type: Improvement >Reporter: Sebb >Assignee: Olivier Lamy > Fix For: ASF-9 > > > There does not appear to be any documentation on the Apache Parent Pom. > Please can the following be added to the next release: > * how to report issues > * where to find the source > Ideally there should be a page on the Maven web-site that documents it as > well. > In which case please link to that from the POM as well. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-606) UnsupportedOperationException on blame GIT
[
http://jira.codehaus.org/browse/SCM-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255592#action_255592
]
Mark Struberg commented on SCM-606:
---
the way to go is to implement this feature for the maven-scm-provider-gitexe
also.
Will do this in the next week.
> UnsupportedOperationException on blame GIT
> --
>
> Key: SCM-606
> URL: http://jira.codehaus.org/browse/SCM-606
> Project: Maven SCM
> Issue Type: Wish
> Components: maven-scm-provider-git
>Affects Versions: 1.4
>Reporter: Fabien Bousquet
>Assignee: Mark Struberg
>Priority: Minor
> Attachments: GitBlame_UnsupportedOperationException.patch
>
>
> Sometimes, running the blame command for GIT return an error for exit code.
> In this case, Maven SCM throw an
> UnsupportedOperationException :
> {code}
> Caused by: java.lang.UnsupportedOperationException
> at
> org.apache.maven.scm.provider.git.gitexe.command.blame.GitBlameCommand.executeBlameCommand(GitBlameCommand.java:46)
> etc...
> {code}
> Is it possible to have the same way that others providers (SVN or TFS for
> example) which is to return a
> result (with a success to false) ?
> In other word replace :
> {code}
> throw new UnsupportedOperationException();
> {code}
> by :
> {code}
> return new BlameScmResult(cl.toString(), "The git command failed.",
> stderr.getOutput(), false);
> {code}
> Another reason is that we do not know that this UnsupportedOperationException
> may be raised because is
> a RuntimeException.
> A similar problem : http://jira.codehaus.org/browse/SONARPLUGINS-618
> Do you agree with 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: (MPOM-1) apache-release does unwanted things in the prepare goal
[ https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993147#comment-12993147 ] Hudson commented on MPOM-1: --- Integrated in ASF Parent Pom #12 (See [https://hudson.apache.org/hudson/job/ASF%20Parent%20Pom/12/]) revert r1065772 see MPOM-1 for updated information > apache-release does unwanted things in the prepare goal > --- > > Key: MPOM-1 > URL: https://issues.apache.org/jira/browse/MPOM-1 > Project: Maven POM > Issue Type: Bug >Reporter: Olivier Lamy >Assignee: Brian Fox > Fix For: ASF-9 > > > Release 7 of the org.apache:apache use -P to turn on an 'apache-release' > profile in the release plugin. By using -P, this profile is turned on in > prepare as well as perform. > This may turn into a contest of opinion, and you all may just tell me to jump > in a lake, but I think this is a bad idea. At prepare time, we're just > looking to get the versions setup and the tag made. Having to deal with gpg > signing, and source archiving seems out of place. > At very least, I'd request that this the element be left out of > the release plugin spec. If some project wants to use that particular > collection of functions, fine. For the rest of us, who just want to get > distribution management and other universals, you we wouldn't have to worry > about it. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-606) UnsupportedOperationException on blame GIT
UnsupportedOperationException on blame GIT
--
Key: SCM-606
URL: http://jira.codehaus.org/browse/SCM-606
Project: Maven SCM
Issue Type: Wish
Components: maven-scm-provider-git
Affects Versions: 1.4
Reporter: Fabien Bousquet
Priority: Minor
Attachments: GitBlame_UnsupportedOperationException.patch
Sometimes, running the blame command for GIT return an error for exit code. In
this case, Maven SCM throw an
UnsupportedOperationException :
{code}
Caused by: java.lang.UnsupportedOperationException
at
org.apache.maven.scm.provider.git.gitexe.command.blame.GitBlameCommand.executeBlameCommand(GitBlameCommand.java:46)
etc...
{code}
Is it possible to have the same way that others providers (SVN or TFS for
example) which is to return a
result (with a success to false) ?
In other word replace :
{code}
throw new UnsupportedOperationException();
{code}
by :
{code}
return new BlameScmResult(cl.toString(), "The git command failed.",
stderr.getOutput(), false);
{code}
Another reason is that we do not know that this UnsupportedOperationException
may be raised because is
a RuntimeException.
A similar problem : http://jira.codehaus.org/browse/SONARPLUGINS-618
Do you agree with 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: (MPOM-1) apache-release does unwanted things in the prepare goal
[ https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993145#comment-12993145 ] Olivier Lamy commented on MPOM-1: - Brian : I agree on your revert np > apache-release does unwanted things in the prepare goal > --- > > Key: MPOM-1 > URL: https://issues.apache.org/jira/browse/MPOM-1 > Project: Maven POM > Issue Type: Bug >Reporter: Olivier Lamy >Assignee: Brian Fox > Fix For: ASF-9 > > > Release 7 of the org.apache:apache use -P to turn on an 'apache-release' > profile in the release plugin. By using -P, this profile is turned on in > prepare as well as perform. > This may turn into a contest of opinion, and you all may just tell me to jump > in a lake, but I think this is a bad idea. At prepare time, we're just > looking to get the versions setup and the tag made. Having to deal with gpg > signing, and source archiving seems out of place. > At very least, I'd request that this the element be left out of > the release plugin spec. If some project wants to use that particular > collection of functions, fine. For the rest of us, who just want to get > distribution management and other universals, you we wouldn't have to worry > about it. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPOM-1) apache-release does unwanted things in the prepare goal
[ https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993143#comment-12993143 ] Brian Fox commented on MPOM-1: -- A little history on this setup: It was moved to the ASF pom from the Maven pom when we tried to provide correct defaults for all ASF projects built with Maven after a lengthy discussion on legal about minimal release requirements. The conclusion was to encapsulate best practices so projects that aren't maven experts can still get meet the release requirements. This particular configuration of the release plugin dates back to the very first setup of the release profiles in the Maven pom, specifically added here: http://svn.apache.org/viewvc?view=revision&revision=502422 a little over 4 years ago. > apache-release does unwanted things in the prepare goal > --- > > Key: MPOM-1 > URL: https://issues.apache.org/jira/browse/MPOM-1 > Project: Maven POM > Issue Type: Bug >Reporter: Olivier Lamy >Assignee: Brian Fox > Fix For: ASF-9 > > > Release 7 of the org.apache:apache use -P to turn on an 'apache-release' > profile in the release plugin. By using -P, this profile is turned on in > prepare as well as perform. > This may turn into a contest of opinion, and you all may just tell me to jump > in a lake, but I think this is a bad idea. At prepare time, we're just > looking to get the versions setup and the tag made. Having to deal with gpg > signing, and source archiving seems out of place. > At very least, I'd request that this the element be left out of > the release plugin spec. If some project wants to use that particular > collection of functions, fine. For the rest of us, who just want to get > distribution management and other universals, you we wouldn't have to worry > about it. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (MPOM-1) apache-release does unwanted things in the prepare goal
[ https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox reassigned MPOM-1: Assignee: Brian Fox (was: Olivier Lamy) > apache-release does unwanted things in the prepare goal > --- > > Key: MPOM-1 > URL: https://issues.apache.org/jira/browse/MPOM-1 > Project: Maven POM > Issue Type: Bug >Reporter: Olivier Lamy >Assignee: Brian Fox > Fix For: ASF-9 > > > Release 7 of the org.apache:apache use -P to turn on an 'apache-release' > profile in the release plugin. By using -P, this profile is turned on in > prepare as well as perform. > This may turn into a contest of opinion, and you all may just tell me to jump > in a lake, but I think this is a bad idea. At prepare time, we're just > looking to get the versions setup and the tag made. Having to deal with gpg > signing, and source archiving seems out of place. > At very least, I'd request that this the element be left out of > the release plugin spec. If some project wants to use that particular > collection of functions, fine. For the rest of us, who just want to get > distribution management and other universals, you we wouldn't have to worry > about it. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4384) Can not use the plexus component org.sonatype.plexus.components.sec.dispatcher.SecDispatcher since maven 2.2.0
[
http://jira.codehaus.org/browse/MNG-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255574#action_255574
]
Tony Chemit commented on MNG-4384:
--
When I will use maven 3.0.2 api I will use SettingsDecrypter component.
Thanks for your replies.
> Can not use the plexus component
> org.sonatype.plexus.components.sec.dispatcher.SecDispatcher since maven 2.2.0
> ---
>
> Key: MNG-4384
> URL: http://jira.codehaus.org/browse/MNG-4384
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 2.2.0, 2.2.1
> Environment: linux
>Reporter: Tony Chemit
>Assignee: Benjamin Bentmann
>
> The SecDispatcher was callable from a plugin before 2.2.0, but not any longer
> :
> {noformat}
> Caused by: org.codehaus.plexus.component.composition.CompositionException:
> Composition failed of field sec in object of type
> org.nuiton.mail.plugin.SendEmailMojo because the requirement
> ComponentRequirement{role='org.sonatype.plexus.components.sec.dispatcher.SecDispatcher',
> roleHint='default', fieldName='sec'} was missing
> at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:154)
> at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assembleComponent(FieldComponentComposer.java:73)
> at
> org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent(DefaultComponentComposerManager.java:68)
> at
> org.codehaus.plexus.DefaultPlexusContainer.composeComponent(DefaultPlexusContainer.java:1486)
> at
> org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:29)
> ... 26 more
> Caused by:
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> Unable to lookup component
> 'org.sonatype.plexus.components.sec.dispatcher.SecDispatcherdefault', it
> could not be started
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:339)
> at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:129)
> ... 30 more
> Caused by:
> org.codehaus.plexus.component.repository.exception.ComponentLifecycleException:
> Error starting component
> at
> org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:109)
> at
> org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:95)
> at
> org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
> ... 31 more
> Caused by:
> org.codehaus.plexus.personality.plexus.lifecycle.phase.PhaseExecutionException:
> Error composing component
> at
> org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:33)
> at
> org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:101)
> at
> org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:105)
> ... 34 more
> Caused by: org.codehaus.plexus.component.composition.CompositionException:
> Composition failed for the field _cipher in object of type
> org.sonatype.plexus.components.sec.dispatcher.DefaultSecDispatcher
> at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:144)
> at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assembleComponent(FieldComponentComposer.java:73)
> at
> org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent(DefaultComponentComposerManager.java:68)
> at
> org.codehaus.plexus.DefaultPlexusContainer.composeComponent(DefaultPlexusContainer.java:1486)
> at
> org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:29)
> ... 36 more
> Caused by: java.lang.IllegalArgumentException: Can not set
> org.sonatype.plexus.components.cipher.PlexusCipher field
> org.sonatype.plexus.components.sec.dispatcher.DefaultSecDispatcher._cipher to
> org.sonatype.plexus.components.cipher.DefaultPlexusCipher
> at
> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:146)
> at
> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeField
[jira] Commented: (MNG-4265) Properties in "system"-scope dependencies breaks transitive dependency resolution
[
http://jira.codehaus.org/browse/MNG-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255571#action_255571
]
Richard Kerr commented on MNG-4265:
---
Seeing this issue in 3.0 and 3.0.2.
> Properties in "system"-scope dependencies breaks transitive dependency
> resolution
> -
>
> Key: MNG-4265
> URL: http://jira.codehaus.org/browse/MNG-4265
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies
>Affects Versions: 2.0.9, 2.0.10, 2.1.0-M1, 2.1.0, 2.2.0
>Reporter: Marc Wilhelm
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: maven-properties-bug.tgz
>
>
> If a used dependency (see artifact "component" in the attached example)
> contains itself a system-scope dependency (here "${JAVA_HOME}/lib/tools.jar")
> with properties, all transitive dependencies are ignored by the following
> warning:
> {code:xml}
> [WARNING] POM for 'maven.bug:component:pom:0.0.1-SNAPSHOT:compile' is invalid.
> Its dependencies (if any) will NOT be available to the current build.
> {code}
> NOTE: The transitive dependencies are handled correctly when building from a
> (reactor) project, which builds both modules, the "component" and the "app".
> But it fails when trying to build the "app" isolated as single project.
> If running the sample project against maven (2.0.4 up to) 2.0.8 it works
> fine, without problems.
> Steps to reproduce:
> - extract sample project
> - ensure environment var JAVA_HOME is set properly
> - build top level project by "mvn clean install". This should build without
> warnings
> - change into sub folder "app"
> - build module "app" via "mvn clean install". You should get the warning
> about an invalid used pom.
--
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-605) More logs when "Terminated with fatal signal 11" with CVS
More logs when "Terminated with fatal signal 11" with CVS
-
Key: SCM-605
URL: http://jira.codehaus.org/browse/SCM-605
Project: Maven SCM
Issue Type: Improvement
Components: maven-scm-provider-cvs
Affects Versions: 1.4
Environment: Windows & Unix
Reporter: Alix Lourme
Priority: Minor
Some problems can affect the scm plugin but not other client (dos, eclipse).
For exemple, a scm config :
{code}
org.apache.maven.plugins
maven-scm-plugin
1.4
target/projectTest
scm:cvs:pserver:@myHost:/myDirectory/myProject:myModule
myUser
myPassword
{code}
Can crash with *mvn scm:checkout* :
{code}
[INFO] [scm:checkout {execution: default-cli}]
[INFO] Removing C:\...\workspace_eclipse\Test\target\ProjectTest
[INFO] Executing: cmd.exe /X /C "cvs -z3 -f -d
:pserver:myUser@myHost:/myDirectory/myProject -q checkout -d ProjectTest
myModule"
[INFO] Working directory: C:\...\workspace_eclipse\Test\target
[ERROR] Provider message:
[ERROR] The cvs command failed.
[ERROR] Command output:
[ERROR] Terminated with fatal signal 11
{code}
The problem is CVS ... but the cause is very hard to diagnostic.
In my case, it was a file of 100 Ko (cvs filesystem Unix), there wasn't problem
with Eclipse's checkout or CVS bin (dos) checkout (same command as SCM use ...
strange).
But there was some problem of commit on this file under Eclipse.
It's relativly easy to solve the problem when you have +the+ file :) ... but to
find it, the only way is :
# SCM's checkout : signal 11 ... so you have not all files
# CVS bin checkout with output saving to have the order of project files
# Make a script doing directory comparaison and have the first file who doesn't
exist in SCM checkout.
A CVS bin write log :
{code}
U myProject/myPackage/File1.java
U myProject/myPackage/File2.java
...
{code}
For each file, I don't know if this log is displayed before of after getting
file, but when scm crash, it would be nice to have the last log line ...
* If the CVS log is printed before getting file, it's the bad file => nice
* If the CVS log is printed after getting file, the message could be "Problem
getting file after : 'U project/[the precedent file who was ok]'"
_And sorry for my worse english_
--
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: (MJARSIGNER-12) It should be possible to save the keystore in one location for multi module projects
It should be possible to save the keystore in one location for multi module projects Key: MJARSIGNER-12 URL: http://jira.codehaus.org/browse/MJARSIGNER-12 Project: Maven 2.x Jar Signer Plugin Issue Type: New Feature Reporter: Sven Kirmess We have a multi module maven setup. The problem is that this plugin requires us to have the keystore either in the same location on all machines or in the source code along each and every pom.xml file. I would like to have one of the following: - Save the file on one location in Subversion and use something like svn://svn.example.com/trunk/keystore and the plugin would have to take care to check out the keystore into every project as needed. or - Put the keystore into a JAR file and save that JAR file on the Nexus server. Then make the jarsigner plugin depend on this JAR file, download it for every project and extract the keystore from there. This would be like what the assembly plugin can do for its descriptors. http://docs.codehaus.org/display/MAVENUSER/Assembly+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] Created: (ARCHETYPE-365) archetype generate does not translate correctly accentuated characters
archetype generate does not translate correctly accentuated characters --- Key: ARCHETYPE-365 URL: http://jira.codehaus.org/browse/ARCHETYPE-365 Project: Maven Archetype Issue Type: Bug Components: Generator Affects Versions: 2.0 Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100) Java version: 1.6.0_23, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_23\jre Default locale: fr_FR, platform encoding: Cp1252 OS name: "windows 2003", version: "5.2", arch: "x86", family: "windows" Reporter: amber Priority: Minor Generating archetype do not preserve accentuated characters. � for "é" The archetype:create work fine and does not alter accentuated characters -- 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-3832) Allow wildcards in dependency exclusions
[
http://jira.codehaus.org/browse/MNG-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255565#action_255565
]
Davor Hrg commented on MNG-3832:
too bad this is still not resolved, with 2 years behind, and 38 votes currently
... and on top of it patches are provided
> Allow wildcards in dependency exclusions
>
>
> Key: MNG-3832
> URL: http://jira.codehaus.org/browse/MNG-3832
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Dependencies
>Reporter: Paul Gier
> Fix For: 3.1
>
> Attachments: MNG-3832-maven-artifact.patch
>
>
> I would like to be able to exclude all transitive dependencies from a certain
> dependencies. This is especially useful when depending on an artifact with a
> classifier that may not have the same dependencies as the main artifact.
> Currently the only way to do this is by excluding each dependency
> individually which requires significant effort and is prone to becoming out
> of date. The following syntax is one possibility.
> Exclude all transitive dependencies
> {code}
>
> *
>
> {code}
> Exclude transitive dependencies with the groupId "org.company"
> {code}
>
> org.company
> *
>
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-4384) Can not use the plexus component org.sonatype.plexus.components.sec.dispatcher.SecDispatcher since maven 2.2.0
[
http://jira.codehaus.org/browse/MNG-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4384.
--
Resolution: Won't Fix
Fix Version/s: (was: Issues to be reviewed for 3.x)
Assignee: Benjamin Bentmann
Going forward, I would like plugins to eventually use
{{[o.a.m.s.crypto.SettingsDecrypter|http://maven.apache.org/ref/3.0.2/maven-settings-builder/apidocs/org/apache/maven/settings/crypto/SettingsDecrypter.html]}}.
In the meantime, this issue can be worked around by depending on
{{plexus-sec-dispatcher}} in compile scope and adding the following
{{src/main/resources/META-INF/components.xml}} to a plugin:
{code:xml}
org.sonatype.plexus.components.sec.dispatcher.SecDispatcher
mng-4384
org.sonatype.plexus.components.sec.dispatcher.DefaultSecDispatcher
org.sonatype.plexus.components.cipher.PlexusCipher
mng-4384
_cipher
<_configuration-file>~/.m2/settings-security.xml
org.sonatype.plexus.components.cipher.PlexusCipher
mng-4384
org.sonatype.plexus.components.cipher.DefaultPlexusCipher
{code}
and in the mojo inject the component via
{code:java}
/** @component role-hint="mng-4384" */
private SecDispatcher secDispatcher;
{code}
Note the role hints used here to avoid problematic clashes with the component
instances from Maven core.
> Can not use the plexus component
> org.sonatype.plexus.components.sec.dispatcher.SecDispatcher since maven 2.2.0
> ---
>
> Key: MNG-4384
> URL: http://jira.codehaus.org/browse/MNG-4384
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 2.2.0, 2.2.1
> Environment: linux
>Reporter: Tony Chemit
>Assignee: Benjamin Bentmann
>
> The SecDispatcher was callable from a plugin before 2.2.0, but not any longer
> :
> {noformat}
> Caused by: org.codehaus.plexus.component.composition.CompositionException:
> Composition failed of field sec in object of type
> org.nuiton.mail.plugin.SendEmailMojo because the requirement
> ComponentRequirement{role='org.sonatype.plexus.components.sec.dispatcher.SecDispatcher',
> roleHint='default', fieldName='sec'} was missing
> at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:154)
> at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assembleComponent(FieldComponentComposer.java:73)
> at
> org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent(DefaultComponentComposerManager.java:68)
> at
> org.codehaus.plexus.DefaultPlexusContainer.composeComponent(DefaultPlexusContainer.java:1486)
> at
> org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:29)
> ... 26 more
> Caused by:
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> Unable to lookup component
> 'org.sonatype.plexus.components.sec.dispatcher.SecDispatcherdefault', it
> could not be started
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:339)
> at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:129)
> ... 30 more
> Caused by:
> org.codehaus.plexus.component.repository.exception.ComponentLifecycleException:
> Error starting component
> at
> org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:109)
> at
> org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:95)
> at
> org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
> ... 31 more
> Caused by:
> org.codehaus.plexus.personality.plexus.lifecycle.phase.PhaseExecutionException:
> Error composing component
> at
> org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:33)
> at
> org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:101)
> at
> org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:105)
> ... 34 more
> Caused by: org.codehaus.plexus.component.composition.CompositionException:
> Composition failed for the field _cipher in object of type
> org.sonatype.plexus.components.sec.dis
[jira] Commented: (MRELEASE-340) Don't store the scm password in plaintext in release.properties
[
http://jira.codehaus.org/browse/MRELEASE-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255561#action_255561
]
Benjamin Bentmann commented on MRELEASE-340:
Not sure since when but recent versions of the plugin support to read the
credentials from the {{settings.xml}}, using the host name part of the SCM URL
as the id to locate a {{}} entry. AFAICT, this approach doesn't leak
the passwords into the {{release.properties}}.
> Don't store the scm password in plaintext in release.properties
> ---
>
> Key: MRELEASE-340
> URL: http://jira.codehaus.org/browse/MRELEASE-340
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
>Reporter: Nap Ramirez
>Priority: Minor
>
> The scm password is stored in plaintext in release.properties file. I think
> it would be safe not to save it there, then always prompt the user for the
> password every time.
--
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: (MRELEASE-648) Putting SVN password in settings.xml doesn't support password encryption
[ http://jira.codehaus.org/browse/MRELEASE-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MRELEASE-648. -- Resolution: Fixed Fix Version/s: 2.2 Assignee: Benjamin Bentmann Supported in [r1069389|http://svn.apache.org/viewvc?view=revision&revision=1069389]. > Putting SVN password in settings.xml doesn't support password encryption > > > Key: MRELEASE-648 > URL: http://jira.codehaus.org/browse/MRELEASE-648 > Project: Maven 2.x Release Plugin > Issue Type: New Feature > Components: scm >Reporter: Julien HENRY >Assignee: Benjamin Bentmann > Fix For: 2.2 > > > I'm using maven-release-plugin-2.0-beta-8 and I have encrypted all the > password in settings.xml as described here: > http://maven.apache.org/guides/mini/guide-encryption.html > It works for deployment servers but not for SVN servers (the functionality > was provided by SCM-85). > I had to revert back to clear passwords for SVN server credentials in > settings.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] Closed: (MSHARED-185) maven-archiver doesn't generate META-INF/maven/groupid/artifactId/pom.* files in JAR
[ http://jira.codehaus.org/browse/MSHARED-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotný closed MSHARED-185. - Resolution: Not A Bug > maven-archiver doesn't generate META-INF/maven/groupid/artifactId/pom.* files > in JAR > > > Key: MSHARED-185 > URL: http://jira.codehaus.org/browse/MSHARED-185 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-archiver >Affects Versions: maven-archiver-2.4, maven-archiver-2.4.1 > Environment: maven 2.2.1/3.0.2, java 6 >Reporter: Marek Novotný >Assignee: Benjamin Bentmann > Attachments: maven-bug.zip, MSHARED-185.zip > > > I am using maven-jar-plugin 2.3.1, which using maven-archiver 2.4.1. In that > configuration in generated jar is not added META-INF/maven/* files. There is > only empty file META-INF/maven. > I tried to donwgrade to maven-jar-plugin 2.2/2.1, which uses maven-archiver > 2.3/2.2 and it works fine - files META-INF/maven/groupId/artifactId/pom.* > files were added/generated. > I tried also to add into archive configuration and > true, although it should be set true > by default, but it doesn't help. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHARED-185) maven-archiver doesn't generate META-INF/maven/groupid/artifactId/pom.* files in JAR
[ http://jira.codehaus.org/browse/MSHARED-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24#action_24 ] Marek Novotný commented on MSHARED-185: --- I can now see the issue, it was in extraction from jar, SORRY! > maven-archiver doesn't generate META-INF/maven/groupid/artifactId/pom.* files > in JAR > > > Key: MSHARED-185 > URL: http://jira.codehaus.org/browse/MSHARED-185 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-archiver >Affects Versions: maven-archiver-2.4, maven-archiver-2.4.1 > Environment: maven 2.2.1/3.0.2, java 6 >Reporter: Marek Novotný >Assignee: Benjamin Bentmann > Attachments: maven-bug.zip, MSHARED-185.zip > > > I am using maven-jar-plugin 2.3.1, which using maven-archiver 2.4.1. In that > configuration in generated jar is not added META-INF/maven/* files. There is > only empty file META-INF/maven. > I tried to donwgrade to maven-jar-plugin 2.2/2.1, which uses maven-archiver > 2.3/2.2 and it works fine - files META-INF/maven/groupId/artifactId/pom.* > files were added/generated. > I tried also to add into archive configuration and > true, although it should be set true > by default, but it doesn't help. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHARED-185) maven-archiver doesn't generate META-INF/maven/groupid/artifactId/pom.* files in JAR
[ http://jira.codehaus.org/browse/MSHARED-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23#action_23 ] Marek Novotný commented on MSHARED-185: --- I should update that I am on linux > maven-archiver doesn't generate META-INF/maven/groupid/artifactId/pom.* files > in JAR > > > Key: MSHARED-185 > URL: http://jira.codehaus.org/browse/MSHARED-185 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-archiver >Affects Versions: maven-archiver-2.4, maven-archiver-2.4.1 > Environment: maven 2.2.1/3.0.2, java 6 >Reporter: Marek Novotný >Assignee: Benjamin Bentmann > Attachments: maven-bug.zip, MSHARED-185.zip > > > I am using maven-jar-plugin 2.3.1, which using maven-archiver 2.4.1. In that > configuration in generated jar is not added META-INF/maven/* files. There is > only empty file META-INF/maven. > I tried to donwgrade to maven-jar-plugin 2.2/2.1, which uses maven-archiver > 2.3/2.2 and it works fine - files META-INF/maven/groupId/artifactId/pom.* > files were added/generated. > I tried also to add into archive configuration and > true, although it should be set true > by default, but it doesn't help. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSHARED-185) maven-archiver doesn't generate META-INF/maven/groupid/artifactId/pom.* files in JAR
[ http://jira.codehaus.org/browse/MSHARED-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotný updated MSHARED-185: -- Attachment: maven-bug.zip zipped built project > maven-archiver doesn't generate META-INF/maven/groupid/artifactId/pom.* files > in JAR > > > Key: MSHARED-185 > URL: http://jira.codehaus.org/browse/MSHARED-185 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-archiver >Affects Versions: maven-archiver-2.4, maven-archiver-2.4.1 > Environment: maven 2.2.1/3.0.2, java 6 >Reporter: Marek Novotný >Assignee: Benjamin Bentmann > Attachments: maven-bug.zip, MSHARED-185.zip > > > I am using maven-jar-plugin 2.3.1, which using maven-archiver 2.4.1. In that > configuration in generated jar is not added META-INF/maven/* files. There is > only empty file META-INF/maven. > I tried to donwgrade to maven-jar-plugin 2.2/2.1, which uses maven-archiver > 2.3/2.2 and it works fine - files META-INF/maven/groupId/artifactId/pom.* > files were added/generated. > I tried also to add into archive configuration and > true, although it should be set true > by default, but it doesn't help. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MSHARED-185) maven-archiver doesn't generate META-INF/maven/groupid/artifactId/pom.* files in JAR
[ http://jira.codehaus.org/browse/MSHARED-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotný reopened MSHARED-185: --- I took your attached maven project and reproduced it. > maven-archiver doesn't generate META-INF/maven/groupid/artifactId/pom.* files > in JAR > > > Key: MSHARED-185 > URL: http://jira.codehaus.org/browse/MSHARED-185 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-archiver >Affects Versions: maven-archiver-2.4, maven-archiver-2.4.1 > Environment: maven 2.2.1/3.0.2, java 6 >Reporter: Marek Novotný >Assignee: Benjamin Bentmann > Attachments: MSHARED-185.zip > > > I am using maven-jar-plugin 2.3.1, which using maven-archiver 2.4.1. In that > configuration in generated jar is not added META-INF/maven/* files. There is > only empty file META-INF/maven. > I tried to donwgrade to maven-jar-plugin 2.2/2.1, which uses maven-archiver > 2.3/2.2 and it works fine - files META-INF/maven/groupId/artifactId/pom.* > files were added/generated. > I tried also to add into archive configuration and > true, although it should be set true > by default, but it doesn't help. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
FW: Class Not found error in Sonar plugin
Hi All, Hi have written a sample plugin for Sonar with only 2 rules. I've generated the archetype. And edited the pom.xml. The pom is attached for reference. When I run mvn clean install, I get the error which says cannot find the class TestPlugin. Any help would be appreciated. Regards, Kabir ATG Developer, Service Creation - eCommerce http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 com.ustri.plugin atgplugin sonar-plugin 1.0-SNAPSHOT Sonar ATG plugin Analyze ATG Jsps My company http://www.mycompany.com org.codehaus.sonar sonar-plugin-api 2.5 org.codehaus.sonar sonar-plugin-api 2.5 org.codehaus.sonar sonar-channel 2.5 provided javax.el el-api 1.0 compile org.jboss.seam jboss-seam 2.2.0.GA compile dom4j dom4j xstream xstream xpp3 xpp3_min xml-apis xml-apis org.codehaus.sonar sonar-testing-harness 2.5 test org.codehaus.sonar sonar-packaging-maven-plugin 1.0 true com.ustri.plugin.TestPlugin org.apache.maven.plugins maven-compiler-plugin 2.0.2 1.5 1.5 UTF-8 repository.jboss.org JBoss Repository http://repository.jboss.org/maven2 codehaus.org Codehaus Repository http://repository.codehaus.org
[jira] Closed: (MSHARED-185) maven-archiver doesn't generate META-INF/maven/groupid/artifactId/pom.* files in JAR
[ http://jira.codehaus.org/browse/MSHARED-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MSHARED-185. - Resolution: Cannot Reproduce Assignee: Benjamin Bentmann > maven-archiver doesn't generate META-INF/maven/groupid/artifactId/pom.* files > in JAR > > > Key: MSHARED-185 > URL: http://jira.codehaus.org/browse/MSHARED-185 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-archiver >Affects Versions: maven-archiver-2.4, maven-archiver-2.4.1 > Environment: maven 2.2.1/3.0.2, java 6 >Reporter: Marek Novotný >Assignee: Benjamin Bentmann > Attachments: MSHARED-185.zip > > > I am using maven-jar-plugin 2.3.1, which using maven-archiver 2.4.1. In that > configuration in generated jar is not added META-INF/maven/* files. There is > only empty file META-INF/maven. > I tried to donwgrade to maven-jar-plugin 2.2/2.1, which uses maven-archiver > 2.3/2.2 and it works fine - files META-INF/maven/groupId/artifactId/pom.* > files were added/generated. > I tried also to add into archive configuration and > true, although it should be set true > by default, but it doesn't help. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSHARED-185) maven-archiver doesn't generate META-INF/maven/groupid/artifactId/pom.* files in JAR
[ http://jira.codehaus.org/browse/MSHARED-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MSHARED-185: -- Attachment: MSHARED-185.zip Works for the attached example, so please consider to provide a runnable project that actually exhibits the issue. > maven-archiver doesn't generate META-INF/maven/groupid/artifactId/pom.* files > in JAR > > > Key: MSHARED-185 > URL: http://jira.codehaus.org/browse/MSHARED-185 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-archiver >Affects Versions: maven-archiver-2.4, maven-archiver-2.4.1 > Environment: maven 2.2.1/3.0.2, java 6 >Reporter: Marek Novotný > Attachments: MSHARED-185.zip > > > I am using maven-jar-plugin 2.3.1, which using maven-archiver 2.4.1. In that > configuration in generated jar is not added META-INF/maven/* files. There is > only empty file META-INF/maven. > I tried to donwgrade to maven-jar-plugin 2.2/2.1, which uses maven-archiver > 2.3/2.2 and it works fine - files META-INF/maven/groupId/artifactId/pom.* > files were added/generated. > I tried also to add into archive configuration and > true, although it should be set true > by default, but it doesn't help. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPDF-46) Remove [WARNING] Deprecated API called
[ http://jira.codehaus.org/browse/MPDF-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated MPDF-46: -- Fix Version/s: 1.2 > Remove [WARNING] Deprecated API called > -- > > Key: MPDF-46 > URL: http://jira.codehaus.org/browse/MPDF-46 > Project: Maven 2.x PDF Plugin > Issue Type: Task >Affects Versions: 1.1 >Reporter: Lukas Theussl > Fix For: 1.2 > > > Happens when including reports in the pdf. -- 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: (MPDF-46) Remove [WARNING] Deprecated API called
Remove [WARNING] Deprecated API called -- Key: MPDF-46 URL: http://jira.codehaus.org/browse/MPDF-46 Project: Maven 2.x PDF Plugin Issue Type: Task Affects Versions: 1.1 Reporter: Lukas Theussl Happens when including reports in the pdf. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-5007) Maven always downloads already existing plugins in my local repository
[ http://jira.codehaus.org/browse/MNG-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-5007. -- Resolution: Incomplete Assignee: Benjamin Bentmann Maven by design doesn't redownload released artifacts. So you either encounter a bug or a misconfiguration/-understanding on your side. In the first case, you might want to re-read the intro page to this issue tracker which gives some hints/instructions regarding proper bug reports. In the latter case, you should ask your question on the [user mailing list|http://maven.apache.org/mail-lists.html]. > Maven always downloads already existing plugins in my local repository > -- > > Key: MNG-5007 > URL: http://jira.codehaus.org/browse/MNG-5007 > Project: Maven 2 & 3 > Issue Type: Wish >Reporter: yusuf coekelekoglu >Assignee: Benjamin Bentmann > > Maven always downloads existing plugins in my .m2 repository. It seems that > it does not matter whether the same plugin already stored in my local > repository or not. How can I configure Maven not always to download those > 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] Created: (MNG-5007) Maven always downloads already existing plugins in my local repository
Maven always downloads already existing plugins in my local repository -- Key: MNG-5007 URL: http://jira.codehaus.org/browse/MNG-5007 Project: Maven 2 & 3 Issue Type: Wish Reporter: yusuf coekelekoglu Maven always downloads existing plugins in my .m2 repository. It seems that it does not matter whether the same plugin already stored in my local repository or not. How can I configure Maven not always to download those 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] Created: (MSHARED-185) maven-archiver doesn't generate META-INF/maven/groupid/artifactId/pom.* files in JAR
maven-archiver doesn't generate META-INF/maven/groupid/artifactId/pom.* files in JAR Key: MSHARED-185 URL: http://jira.codehaus.org/browse/MSHARED-185 Project: Maven Shared Components Issue Type: Bug Components: maven-archiver Affects Versions: maven-archiver-2.4.1, maven-archiver-2.4 Environment: maven 2.2.1/3.0.2, java 6 Reporter: Marek Novotný I am using maven-jar-plugin 2.3.1, which using maven-archiver 2.4.1. In that configuration in generated jar is not added META-INF/maven/* files. There is only empty file META-INF/maven. I tried to donwgrade to maven-jar-plugin 2.2/2.1, which uses maven-archiver 2.3/2.2 and it works fine - files META-INF/maven/groupId/artifactId/pom.* files were added/generated. I tried also to add into archive configuration and true, although it should be set true by default, but it doesn't help. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
