David Smiley created MDEP-661:
-
Summary: Add option to exclude optional dependencies for
copy-dependencies
Key: MDEP-661
URL: https://issues.apache.org/jira/browse/MDEP-661
Project: Maven Dependency
[
http://jira.codehaus.org/browse/MNG-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=233796#action_233796
]
David Smiley commented on MNG-2066:
---
I'm shocked so perhaps I'm misunderstanding things. I work in
Doesn't understand default file paths
-
Key: WAGON-268
URL: http://jira.codehaus.org/browse/WAGON-268
Project: Maven Wagon
Issue Type: Bug
Components: wagon-provider-api
Reporter:
[
http://jira.codehaus.org/browse/MNG-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=150300#action_150300
]
David Smiley commented on MNG-468:
--
If this is closed then how do I use this feature? I found this:
install:install-file should default to a pom file found in the jar if available
---
Key: MINSTALL-52
URL: http://jira.codehaus.org/browse/MINSTALL-52
Project: Maven 2.x
[
http://jira.codehaus.org/browse/MCOMPILER-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133365#action_133365
]
David Smiley commented on MCOMPILER-65:
---
Great, it appears that this new Toolchains feature
Artifact information (seen via search or browse) should show which repository
it's in
-
Key: MRM-779
URL: http://jira.codehaus.org/browse/MRM-779
Project: Archiva
search should tokenize on a hypthen
---
Key: MRM-732
URL: http://jira.codehaus.org/browse/MRM-732
Project: Archiva
Issue Type: Improvement
Components: indexing
Affects Versions: 1.0
Bad checksums
-
Key: MEJB-31
URL: http://jira.codehaus.org/browse/MEJB-31
Project: Maven 2.x Ejb Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: maven 2.0.8
Reporter: David Smiley
I get the
[
http://jira.codehaus.org/browse/MEAR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122135
]
David Smiley commented on MEAR-83:
--
What you say is fair... though this hurts my maven experience a bit. The
specific error
Intelligent fork or bootclasspath based on desired target JDK
-
Key: MCOMPILER-65
URL: http://jira.codehaus.org/browse/MCOMPILER-65
Project: Maven 2.x Compiler Plugin
Issue Type:
[
http://jira.codehaus.org/browse/MCOMPILER-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122035
]
David Smiley commented on MCOMPILER-65:
---
I was about to suggest that adding a targetVendor attribute would address
Documentation refers to jarModule instead of javaModule but jarModule doesn't
seem to be released yet
-
Key: MEAR-83
URL: http://jira.codehaus.org/browse/MEAR-83
[ http://jira.codehaus.org/browse/MRELEASE-62?page=comments#action_81811 ]
David Smiley commented on MRELEASE-62:
--
As of this date, release:prepare appears not to run the install phase. I
looked in my local repo and I didn't find the
[ http://jira.codehaus.org/browse/MRELEASE-57?page=comments#action_79258 ]
David Smiley commented on MRELEASE-57:
--
I still have this problem, if this is the one I think it is. I am forced to
specify the tagBase. Here's my scm.connection
[ http://jira.codehaus.org/browse/MEV-425?page=comments#action_70390 ]
David Smiley commented on MEV-425:
--
Actually... this isn't causing junit to show up in my war file; it was
something else that I fixed. Nonetheless... someone should
plexus-container-default, junit scope compile is bad
Key: MEV-425
URL: http://jira.codehaus.org/browse/MEV-425
Project: Maven Evangelism
Issue Type: Bug
Components: Dependencies
Have Java code output Java version, not the shell script
Key: MNG-2376
URL: http://jira.codehaus.org/browse/MNG-2376
Project: Maven 2
Type: Improvement
Components: Command Line
Versions: 2.0.4
XSLT for converting Maven1 project.xml to Maven2 pom.xml
Key: MNG-2337
URL: http://jira.codehaus.org/browse/MNG-2337
Project: Maven 2
Type: Task
Components: Documentation: Guides
Versions: 2.0.4
[ http://jira.codehaus.org/browse/MEV-394?page=all ]
David Smiley updated MEV-394:
-
Attachment: axis-1.4.pom
Axis' dependencies aren't specified in ibiblio
--
Key: MEV-394
URL:
[ http://jira.codehaus.org/browse/MEV-394?page=comments#action_65925 ]
David Smiley commented on MEV-394:
--
Perhaps there may be a little bit of confusion. The groupId, artifactId and
packaging are wrong in the file I attached; sorry. I meant to leave
[ http://jira.codehaus.org/browse/MNG-1337?page=comments#action_65945 ]
David Smiley commented on MNG-1337:
---
Are you sure this is fixed? When I try to reference ${pom.build.directory}
from a module, I get nothing.
Interpolation of POM values needs to
[ http://jira.codehaus.org/browse/MANTRUN-37?page=comments#action_65954 ]
David Smiley commented on MANTRUN-37:
-
I am also seeing this very same problem. Specifying v1.0 does remove the bug.
I also am using xdoclet, as Frederik is too. Please reopen
relative path of webResources in parent pom not anchored correctly when run
from parent
---
Key: MWAR-42
URL: http://jira.codehaus.org/browse/MWAR-42
Project: Maven 2.x War Plugin
Axis' dependencies aren't specified in ibiblio
--
Key: MEV-394
URL: http://jira.codehaus.org/browse/MEV-394
Project: Maven Evangelism
Type: Improvement
Components: Dependencies
Reporter: David Smiley
Attachments:
[ http://jira.codehaus.org/browse/MEV-394?page=all ]
David Smiley updated MEV-394:
-
Attachment: axis-1.4.pom
Axis' dependencies aren't specified in ibiblio
--
Key: MEV-394
URL:
[ http://jira.codehaus.org/browse/MNG-1012?page=comments#action_65286 ]
David Smiley commented on MNG-1012:
---
I understand that it needs to be standalone.
Perhaps when a POM is deployed to a repository, the groupId, artifactId, and
version could be
27 matches
Mail list logo
