[ http://jira.codehaus.org/browse/MNGECLIPSE-103?page=all ]
Scott Cytacki updated MNGECLIPSE-103:
-
Attachment: maven-plugin-launch-bug.zip
> Multiple projects launch configuration name collision
>
wizard for creating java project from existing pom.xml
--
Key: MNGECLIPSE-134
URL: http://jira.codehaus.org/browse/MNGECLIPSE-134
Project: Maven 2.x Extension for Eclipse
Type: New Feature
Components: Wizards
Documentation of the @component javadoc tag
---
Key: MNG-2355
URL: http://jira.codehaus.org/browse/MNG-2355
Project: Maven 2
Type: Improvement
Components: Documentation: General
Reporter: Scott Cytacki
While trying
[ http://jira.codehaus.org/browse/MNGECLIPSE-134?page=comments#action_66980
]
Scott Cytacki commented on MNGECLIPSE-134:
--
Here are the steps I have to do when checking out a simple maven project:
- give it a name: there is no default name suggested
[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=all ]
Scott Cytacki updated MNGECLIPSE-59:
Attachment: project-artifacts.patch
> Allow artifact resolution from workspace projects
> -
>
> K
[ http://jira.codehaus.org/browse/MNGECLIPSE-106?page=comments#action_67837
]
Scott Cytacki commented on MNGECLIPSE-106:
--
I've found a way to have a maven project double as a eclipse plugin. I don't
know if this solves your particular problem but
dependencyManagement in parent poms broken in eclipse on linux
--
Key: MNGECLIPSE-145
URL: http://jira.codehaus.org/browse/MNGECLIPSE-145
Project: Maven 2.x Extension for Eclipse
Type: Bug
Components: Dep
[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_68375
]
Scott Cytacki commented on MNGECLIPSE-59:
-
Hi Dimitry and Eugene,
I'm sorry for any confusion that I caused, but I assumed that Kenney's patch
was the most uptodate. Base
[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_68386
]
Scott Cytacki commented on MNGECLIPSE-59:
-
After looking more closely at the two patches: Mark's and Kenney's. I realized
they are not the same. Kenney did add the eclips
[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=all ]
Scott Cytacki updated MNGECLIPSE-59:
Attachment: project-artifacts-2006062701.patch
> Allow artifact resolution from workspace projects
> -
>
>
[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=all ]
Scott Cytacki updated MNGECLIPSE-59:
Attachment: project-artifacts-2006062900.patch
> Allow artifact resolution from workspace projects
> -
>
>
handle signing jars which are not project artifacts and not "in place" signing
--
Key: MJAR-51
URL: http://jira.codehaus.org/browse/MJAR-51
Project: Maven 2.x Jar Plugin
[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_71776
]
Scott Cytacki commented on MNGECLIPSE-59:
-
I just checked the attachements and it seems they are back. I see that this
issue has been marked unassigned.
Ca
Documentation of Deployment Repository Directory
Key: CONTINUUM-811
URL: http://jira.codehaus.org/browse/CONTINUUM-811
Project: Continuum
Issue Type: Bug
Components: Documentation
[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_72391
]
Scott Cytacki commented on MNGECLIPSE-59:
-
The embedder has been updated already to include the changes: MNG-1937
The embedder checked into the m2eclipse svn inc
[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_72473
]
Scott Cytacki commented on MNGECLIPSE-59:
-
Dimitry, some testing would be great.
Robert,
Regarding the duplicate project dependencies. I would expect the JDT t
Use eclipse artifact resolver for forked maven builds
-
Key: MNGECLIPSE-179
URL: http://jira.codehaus.org/browse/MNGECLIPSE-179
Project: Maven 2.x Extension for Eclipse
Issue Type: New Feat
Eclipse artifact resolver doesn't handle multi-module projects
--
Key: MNGECLIPSE-180
URL: http://jira.codehaus.org/browse/MNGECLIPSE-180
Project: Maven 2.x Extension for Eclipse
Is
[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_72482
]
Scott Cytacki commented on MNGECLIPSE-59:
-
created MNGECLIPSE-179 to dicuss this option of using the resolver in forked
maven builds.
created MNGECLIPSE-180 to
[ http://jira.codehaus.org/browse/MNGECLIPSE-179?page=comments#action_72483
]
Scott Cytacki commented on MNGECLIPSE-179:
--
That use case definately trumps any complications in the local repository.
One part of the solution could be to
[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_72565
]
Scott Cytacki commented on MNGECLIPSE-59:
-
I just checked it out. The refactoring looks good, and thanks for updating the
eclipse formater settings. But...
I
[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_72627
]
Scott Cytacki commented on MNGECLIPSE-59:
-
I think I tracked down the source of my problems. The artifacts map in the
MavenModelManager is not be initialized c
Initialization of the artifact map, and initialization after cleaning.
--
Key: MNGECLIPSE-182
URL: http://jira.codehaus.org/browse/MNGECLIPSE-182
Project: Maven 2.x Extension for Ecli
invalid relativePath references in pom causes an incorrectly handled NPE
Key: MNGECLIPSE-184
URL: http://jira.codehaus.org/browse/MNGECLIPSE-184
Project: Maven 2.x Extension for
[ http://jira.codehaus.org/browse/MNGECLIPSE-182?page=all ]
Scott Cytacki updated MNGECLIPSE-182:
-
Attachment: model-mananger-init-20060818-0.patch
This patch takes care of the problems for me. It schedules a job for
collecting all the poms in the
[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_72701
]
Scott Cytacki commented on MNGECLIPSE-59:
-
I created a sub-task to work on the patch for initializing the artifact map:
MNGECLIPSE-182
I've posted a patch there
[ http://jira.codehaus.org/browse/MJAR-14?page=comments#action_77596 ]
Scott Cytacki commented on MJAR-14:
---
Another consequence of putting the exporte-pom.xml in the jar is that any
properties defined in the settings.xml end up in the jar. Thi
examples/webapp.html documentation is incorrect
-
Key: ARCHETYPE-113
URL: http://jira.codehaus.org/browse/ARCHETYPE-113
Project: Maven Archetype
Issue Type: Bug
Reporter: Scott Cy
28 matches
Mail list logo
