No, I was responding to Marcus Malcom who is offtopic.
On 13 November 2013 09:52, Mauro Condarelli <mc5...@mclink.it> wrote:
> Sorry,
> I do not understand.
> I did NOT import the projects, I created them and then exported to SVN.
> You mean I should clear everything (switch to a new workspace) and
> re-import the projects?
>
> To confuse matters further I am using com.zenjava::javafx-maven-plugin
> which seems not to understand at all ${...} constructs.
>
> I am pretty sure some (at least) of my problems are unrelated to eclipse,
> but I'm unsure where to ask for support.
>
> Regards
> Mauro
>
>
>
> On 13/11/2013 15:24, Matthew Piggott wrote:
>
> In preferences turn on "Hide folders of physically nested modules" and
> re-import your projects.
>
>
> On 12 November 2013 18:42, Marcus Malcom <malcomm...@gmail.com> wrote:
>
>> Just to be sure, the current m2e should cover multi module projects w/o
>> issue.
>>
>> *One thing:* multi module maven projects will map to Eclipse projects
>> not as cleanly as one would want. The parent project will show and all the
>> child modules folders, but you will also have each child module as an
>> Eclipse project. There's a lot of discussion on this, this one talks about
>> it: Sub-Projects in eclipse<http://www.eclipse.org/forums/index.php/t/84363/>
>> .
>>
>> Agreed with the maven release plugin, working with multi module
>> projects these commands really help:
>>
>> mvn release:set
>> mvn release:commit
>>
>> Full list of commands can be found here:
>> maven-release-plugin<http://maven.apache.org/maven-release/maven-release-plugin/>
>> .
>>
>> Hope that helps.
>>
>> --
>> Marcus
>>
>>
>>
>>
>> On Tue, Nov 12, 2013 at 3:22 PM, Adrien Rivard
>> <adrien.riv...@gmail.com>wrote:
>>
>>> You may also want to look at the maven-release-plugin,
>>> the buildnumber-maven-plugin and maybe the versions-maven-plugin.
>>>
>>> Apart from that I think you are trying to do things with m2e that it
>>> does not really cover.
>>> All the stuff like packaging releasing... are expected to be done via
>>> plain maven (or eventually via the equivalent "run as maven ..." .
>>>
>>>
>>>
>>> On Wed, Nov 13, 2013 at 12:02 AM, Marcus Malcom
>>> <malcomm...@gmail.com>wrote:
>>>
>>>> This isn't exactly m2e related, but you will want to do a google search
>>>> on "maven multi module" and you should get what you need. Taking a quick
>>>> look, this seems pretty nice:
>>>>
>>>> http://books.sonatype.com/mvnex-book/reference/multimodule.html
>>>>
>>>> Hope this helps.
>>>>
>>>> --
>>>> Marcus
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, Nov 12, 2013 at 2:51 PM, Mauro Condarelli <mc5...@mclink.it>wrote:
>>>>
>>>>> Hi,
>>>>> First of all a disclaimer: I am a quite used to eclipse, but a newbie
>>>>> to maven, so please be lenient if I ask stupid (or plain obvious)
>>>>> questions
>>>>> and redirect me to the Right Manual (TM).
>>>>>
>>>>> I have a non-trivial program composed by three eclipse projects, plus
>>>>> one that's used just for building.
>>>>>
>>>>> I sat up the projects giving the standard version: 1.0.0-SNAPSHOT and
>>>>> this is working, building everything and producing a deployable set of
>>>>> files (jars, runtime and launcher).
>>>>> So far, so good.
>>>>>
>>>>> Now I'm approaching delivery and I need to switch from SNAPSHOT to
>>>>> releases.
>>>>> I tried changing manually the versions (1.0.0-SNAPSHOT -> 1.0.1) but
>>>>> that screws completely dependencies.
>>>>>
>>>>> I would like:
>>>>> 1) to have the version stored only in one place (the master POM).
>>>>> 2) get dependency handling (all modules/projects should have the same
>>>>> version number).
>>>>> 3) have automatic versioning (the last number in the version triplet
>>>>> should be the SVN commit number).
>>>>>
>>>>> I think all this is possible (I've found references all over the
>>>>> internet, but they were for pain maven, not for maven handled by eclipse),
>>>>> but all my attempts have met failure.
>>>>>
>>>>> Can someone be so kind to point me in the right direction, pretty
>>>>> please?
>>>>>
>>>>> Thanks in Advance
>>>>> Mauro
>>>>> _______________________________________________
>>>>> m2e-users mailing list
>>>>> m2e-users@eclipse.org
>>>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> m2e-users mailing list
>>>> m2e-users@eclipse.org
>>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>>>
>>>>
>>>
>>>
>>> --
>>> Adrien Rivard
>>>
>>> _______________________________________________
>>> m2e-users mailing list
>>> m2e-users@eclipse.org
>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>>
>>>
>>
>> _______________________________________________
>> m2e-users mailing list
>> m2e-users@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>
>>
>
>
> _______________________________________________
> m2e-users mailing
> listm2e-users@eclipse.orghttps://dev.eclipse.org/mailman/listinfo/m2e-users
>
>
>
> _______________________________________________
> m2e-users mailing list
> m2e-users@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/m2e-users
>
>
_______________________________________________
m2e-users mailing list
m2e-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/m2e-users
