Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] Request to confirm my understanding of how plugin lifecycle mapping works ...
I haven't looked at what you attached in the other message, but you might want to ensure your build.properties are accurate and nothing is missing from the build output.  These problems don't necessarily cause problems when you're self-hosting.  If you haven't tried already, it is possible to remotely debug Eclipse by adding the vm args to your eclipse.ini

Matthew

On 27 May 2011 09:38, Benson Margulies <bimargulies@xxxxxxxxx> wrote:
Igor,

redundantly, I want to point out that I'm stuck. I've apparently made
some stupid mistake that causes my plugins not to install properly
with 0.13/3.7. Unless I have some inspiration, I await m2e devs
deciding that my code's ability to provoke m2e core into creating
'problems' with description 'null' is worthy of your attention.

--benson


On Tue, May 17, 2011 at 10:45 AM, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
> Maven repo can be used for single-artifact extensions. Using checkstyle
> as an example, if this is just one bundle, give us repository url and
> bundle's groupId/artifactId/version and our tool will generate all
> necessary metadata to make this bundle installable from m2e marketplace.
>
> Anything more complex, i.e. features with one or more bundles, has to
> come from a p2 repository.
>
> --
> Regards,
> Igor
>
> On 11-05-17 10:25 AM, Benson Margulies wrote:
>>
>> A maven repo? Does this mean I can publish to ossrh? Just publish the
>> osgi artifacts for the plugins and features?
>>
>>
>>
>> On Tue, May 17, 2011 at 10:17 AM, Igor Fedorenko<igor@xxxxxxxxxxxxxx>
>>  wrote:
>>>
>>> For each extension you want to publish to m2e marketplace we need
>>>
>>> 1. name, description and summary (don't ask what's the difference
>>> between the last two)
>>> 2. license and provider information
>>> 3. where we can get artifacts from. can either be a p2 or maven
>>> repository.
>>> 4. sample project and steps to see your extension in action
>>>
>>> Open bugzilla ticket with this info and add [catalog] to the subject
>>> line so we can tell what it is easily.
>>>
>>> You can see this info for existing entries in [1]
>>>
>>> [1]
>>>
>>> http://git.eclipse.org/c/m2e/m2e-core.git/tree/org.eclipse.m2e.discovery-directory/org.eclipse.m2e.discovery.oss/connectors.xml
>>>
>>> --
>>> Regards,
>>> Igor
>>>
>>> On 11-05-16 06:12 AM, Benson Margulies wrote:
>>>>
>>>> I'd be happy to get this into the marketplace, please send more info
>>>> in what I have to do.
>>>>
>>>> Yes it seems to work, but I haven't exahustively tested it.
>>>>
>>>> On Sun, May 15, 2011 at 11:09 PM, Igor Fedorenko<igor@xxxxxxxxxxxxxx>
>>>>  wrote:
>>>>>
>>>>> Yes, this looks good. Does it actually work?
>>>>>
>>>>> One clarification, lifecycle mapping only affects workspace project
>>>>> configuration and workspace builds, it has no effect on RunAs->Maven
>>>>> actions.
>>>>>
>>>>> Also, if you are interested, we can add checkstyle and pmd integration
>>>>> to m2e marketplace. This will allow m2e automatically discover and
>>>>> offer
>>>>> installation of checkstyle and pmd integration for any project that
>>>>> uses
>>>>> corresponding maven plugins. After you get this working properly and
>>>>> testing, of course ;-)
>>>>>
>>>>> --
>>>>> Regards,
>>>>> Igor
>>>>>
>>>>> On 11-05-15 09:11 PM, Benson Margulies wrote:
>>>>>>
>>>>>> My goal is this: if the POM configures checkstyle, then (a) configure
>>>>>> the Checkstyle plugin for eclipse, and (b) don't execute the execution
>>>>>> from the POM when running Maven from Eclipse. I have the following by
>>>>>> cargo-cult copying from antlr. Have I got it right-ish?
>>>>>>
>>>>>>
>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>> <lifecycleMappingMetadata>
>>>>>>        <pluginExecutions>
>>>>>>                <pluginExecution>
>>>>>>                        <pluginExecutionFilter>
>>>>>>
>>>>>>  <groupId>org.apache.maven.plugins</groupId>
>>>>>>
>>>>>>  <artifactId>maven-checkstyle-plugin</artifactId>
>>>>>>                                <versionRange>[2.6,)</versionRange>
>>>>>>                                <goals>
>>>>>>                                        <goal>checkstyle</goal>
>>>>>>                                </goals>
>>>>>>                        </pluginExecutionFilter>
>>>>>>                        <action>
>>>>>>                                <configurator>
>>>>>>
>>>>>>  <id>com.basistech.m2e.code.quality.checkstyleConfigurator</id>
>>>>>>                                </configurator>
>>>>>>                        </action>
>>>>>>                </pluginExecution>
>>>>>>                <!-- add in the other checkstyle plugin goal? -->
>>>>>>        </pluginExecutions>
>>>>>> </lifecycleMappingMetadata>
>>>>>
>>>>> _______________________________________________
>>>>> m2e-dev mailing list
>>>>> m2e-dev@xxxxxxxxxxx
>>>>> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>>>>>
>>>> _______________________________________________
>>>> m2e-dev mailing list
>>>> m2e-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>>>
>>> _______________________________________________
>>> m2e-dev mailing list
>>> m2e-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>>>
>> _______________________________________________
>> m2e-dev mailing list
>> m2e-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>
> _______________________________________________
> m2e-dev mailing list
> m2e-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev

Back to the top