geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevan Miller (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (GERONIMODEVTOOLS-282) Classpath entries to resources in SharedLIb incorrect causing them not to be found when running on the Geronimo server
Date Sat, 16 Feb 2008 23:13:10 GMT

     [ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kevan Miller reopened GERONIMODEVTOOLS-282:
-------------------------------------------


Tim,
As Donald pointed out previously on the dev list, one of your commits for this issue updated
tagged code -- http://svn.apache.org/viewvc?view=rev&revision=627785

This change needs to be reverted. I assume you'll want to create a branches/2.0 directory
to generate a new 2.0.1 release of the geronimo plugin?

Something like the following should create a new branches 2.0

svn cp https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.0.0 https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.0
--message "GERONIMODEVTOOLS-282 Create 2.0.x branch"

Then the following should undo your commit to tags/2.0.0

svn merge -r 627785: 627784 https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.0.0
--message "GERONIMODEVTOOLS-282 undo commit to tags/2.0.0"

> Classpath entries to resources in SharedLIb incorrect causing them not to be found when
running on the Geronimo server
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMODEVTOOLS-282
>                 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-282
>             Project: Geronimo-Devtools
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Tim McConnell
>            Assignee: Tim McConnell
>             Fix For: 2.0.2, 2.0.x, 2.1.0
>
>
> The GEP is duplicating the output folder in classpath entries for resources in the sharedlib
manifest entry. For example, for a project with a name of project1 in the Eclipse workspace
the classpath entry in the manifest shows up as:
> file:/C:/workspace/projects/project1/target/classes/
> file:/C:/workspace/projects/project1/project1/src/main/resources/
> file:/C:/workspace/projects/project1/project1/src/test/resources/
> When they should be:
> file:/C:/workspace/projects/project1/target/classes/
> file:/C:/workspace/projects/project1/src/main/resources/
> file:/C:/workspace/projects/project1/src/test/resources/

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message