[ 
https://jira.codehaus.org/browse/MECLIPSE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330274#comment-330274
 ] 

Gabriele Catania commented on MECLIPSE-575:
-------------------------------------------

The patch available on github has a lot of spurious changes due to different 
source code formatting.

The patch attached to this issue looks cleaner than my dirty implementation 
attached in MECLIPSE-719, but lacks unit tests (You could merge those from the 
last patch attached to MECLIPSE-719).

My question about this issue on the maven developers list got the following 
answer:
{quote}"to-maven" was always a stop-gap measure until Eclipse started hosting
with their artifacts as a Maven Repository.
See
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=283745 "Provide Maven
repositories of stuff built at Eclipse "
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=312656 "Publish Helios
as a Maven repository" [Resolved as WONT]

But we are still waiting.

Given PDE Maven Plugin has been End-Of-Life'd your only other option
is to build via Tycho (http://eclipse.org/tycho/)

Attempting to use to-maven will probably cause you grief.{quote}
                
> eclipse:to-maven and source packages
> ------------------------------------
>
>                 Key: MECLIPSE-575
>                 URL: https://jira.codehaus.org/browse/MECLIPSE-575
>             Project: Maven Eclipse Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.7
>         Environment: Maven 2.1
>            Reporter: Lukasz Dywicki
>         Attachments: source-classifier.patch, source-classifier.patch
>
>
> Running eclipse:to-maven goal on any eclispe installation will deploy 
> artifacts like 
> org.eclipse.wst.xsl.jaxp.debug.ui.source_1.0.0.v200904240436.jar
> to repository with artifactId = source. In fact the source is information 
> about package contents and in Maven world it's classifier.
> Provided patch checks file names and *deploy* source artifacts attached to 
> plugins.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to