What about a repository of pre-made wrapper modules?

[Fabrizio Giudici]

Is it something that we should do at community level? Please read and
comment:

http://netbeans.dzone.com/news/nb-power-repository-ready-use


Thanks.

--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog
Fabrizio.Giudici@... - mobile: [phone]

[Adam Kędziora]

Dnia poniedziałek 19 października 2009 o 16:27:16 Fabrizio Giudici napisał(a):
> Is it something that we should do at community level? Please read and
> comment:
>
> http://netbeans.dzone.com/news/nb-power-repository-ready-use
>
>
> Thanks.
>
it would be hell usefull to me :P - alongside with the nb platform project
moved to mavven by default and platform chosen from the repo like this one -
it would soooooo simplify work on the platform apps in the group enviroment -
especialy in mixed IDE enviroment (let's face it - currently it requires a lot
of ant work to manage setup like this :P)
--
pozdrawiam
Adam Kędziora

[David Beer-2]

On Mon, 2009-10-19 at 16:41 +0200, Adam Kędziora wrote:

> Dnia poniedziałek 19 października 2009 o 16:27:16 Fabrizio Giudici napisał(a):
> > Is it something that we should do at community level? Please read and
> > comment:
> >
> > http://netbeans.dzone.com/news/nb-power-repository-ready-use
> >
> >
> > Thanks.
> >
> it would be hell usefull to me :P - alongside with the nb platform project
> moved to mavven by default and platform chosen from the repo like this one -
> it would soooooo simplify work on the platform apps in the group enviroment -
> especialy in mixed IDE enviroment (let's face it - currently it requires a lot
> of ant work to manage setup like this :P)

I am not currently using Maven for my NB platform projects or others,
but could see a benefit in using it in the future. I could seed how a
central repository could be useful.


--
Thanks

David

[Florian Brunner]

Hi Fabrizio,

I started a similar discussion about one year ago. You can read it here:
http://markmail.org/message/ls6nncbwd3k3smgn#query:related%3Als6nncbwd3k3smgn+page:2+mid:nwv73jop5j76bu6t+state:results

-Florian

Fabrizio Giudici schrieb:
> Is it something that we should do at community level? Please read and
> comment:
>
> http://netbeans.dzone.com/news/nb-power-repository-ready-use
>
>
> Thanks.
>

[Fabrizio Giudici]

Florian Brunner wrote:
> Hi Fabrizio,
>
> I started a similar discussion about one year ago. You can read it
> here:
> http://markmail.org/message/ls6nncbwd3k3smgn#query:related%3Als6nncbwd3k3smgn+page:2+mid:nwv73jop5j76bu6t+state:results

Thanks for pointing it out. I missed it or completely forgot about it - or probably I decimated it when I read the first 'maven' :-) Did you do something about that in the past year?


--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog
Fabrizio.Giudici@... - mobile: [phone]

[Florian Brunner]

No, since I'm not familiar with Maven and was new to the NetBeans
Platform, too, I didn't do anything in that field yet.

How well do Maven and the NetBeans Platform work together? Is everthing
supported by Ant also supported by Maven? (building, running, debugging,
profiling 'normal' and JNLP variant from within the IDE, building NBM,
and WAR from outside the NBM etc.)

Maybe the NetBeans team should consider to switch to Maven then, as the
default building platform, so also new users can easily profit from a
common module repository? What do you think?

-Florian

Fabrizio Giudici schrieb:

> Florian Brunner wrote:
> > Hi Fabrizio,
>
> >
>
> > I started a similar discussion about one year ago. You can read it
>
> > here:
>
> >
> http://markmail.org/message/ls6nncbwd3k3smgn#query:related%3Als6nncbwd3k3smgn+page:2+mid:nwv73jop5j76bu6t+state:results
>
>
>
> Thanks for pointing it out. I missed it or completely forgot about it
> - or probably I decimated it when I read the first 'maven' :-) Did you
> do something about that in the past year?
>
>
> --
> Fabrizio Giudici - Java Architect, Project Manager
> Tidalwave s.a.s. - "We make Java work. Everywhere."
> weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog
> Fabrizio.Giudici@... - mobile: [phone]
>

[tomwheel]

On Tue, Oct 20, 2009 at 4:42 AM, Florian Brunner <fbrunnerlist@...> wrote:
> Maybe the NetBeans team should consider to switch to Maven then, as the
> default building platform

I see from the Wiki that it's at least under consideration:

   http://wiki.netbeans.org/MavenizingNbbuildProsAndCons


--
Tom Wheeler
http://www.tomwheeler.com/

[Florian Brunner]

Thanks for the link. It seems it's quite recently under discussion:
http://wiki.netbeans.org/PageInfo.jsp?page=MavenizingNbbuildProsAndCons

:-)

Tom Wheeler schrieb:

> On Tue, Oct 20, 2009 at 4:42 AM, Florian Brunner <fbrunnerlist@...> wrote:
>  
>> Maybe the NetBeans team should consider to switch to Maven then, as the
>> default building platform
>>    
>
> I see from the Wiki that it's at least under consideration:
>
>    http://wiki.netbeans.org/MavenizingNbbuildProsAndCons
>
>
>  

[Fabrizio Giudici]

Florian Brunner wrote:
> Thanks for the link. It seems it's quite recently under discussion:
> http://wiki.netbeans.org/PageInfo.jsp?page=MavenizingNbbuildProsAndCons
>
Indeed, there's an impact to the release cycle. I've seen it (and
perhaps resolved) on my projects, figure out what's the impact on a
large project such as NetBeans. I'm not saying it can't be done, of
course: I'm saying that it needs some deep investigation by the NB guys
before deciding.

In any case, this is probably the most annoying bug:

- maven-release-plugin support for Mercurial may be poor. (mkleint:
Agreed. The way release plugin works with svn is not easily
transplantable to hg. For each release it creates a new branch/tag,
effectively copying the sources. In hg world it would mean forking a new
clone. and there's no way to branch/tag just part of the hg repository.
So each module's release could trigger new tag/branch on the whole repo
(tag probably cheaper) For more, See Versions section below)

It's a stupid thing that Maven does - at each release the whole hg
repository is cloned *from the remote repository*, and you figure out
that NetBeans repo is 1.5GB.

--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog
Fabrizio.Giudici@... - mobile: [phone]

[Florian Brunner]

Fabrizio Giudici schrieb:

> Florian Brunner wrote:
>> Thanks for the link. It seems it's quite recently under discussion:
>> http://wiki.netbeans.org/PageInfo.jsp?page=MavenizingNbbuildProsAndCons
>>
> Indeed, there's an impact to the release cycle. I've seen it (and
> perhaps resolved) on my projects, figure out what's the impact on a
> large project such as NetBeans. I'm not saying it can't be done, of
> course: I'm saying that it needs some deep investigation by the NB
> guys before deciding.
>
> In any case, this is probably the most annoying bug:
>
> - maven-release-plugin support for Mercurial may be poor. (mkleint:
> Agreed. The way release plugin works with svn is not easily
> transplantable to hg. For each release it creates a new branch/tag,
> effectively copying the sources. In hg world it would mean forking a
> new clone. and there's no way to branch/tag just part of the hg
> repository. So each module's release could trigger new tag/branch on
> the whole repo (tag probably cheaper) For more, See Versions section
> below)
>
> It's a stupid thing that Maven does - at each release the whole hg
> repository is cloned *from the remote repository*, and you figure out
> that NetBeans repo is 1.5GB.
>

Maybe someone can file an issue to Maven then? Or maybe even provide a
patch?

-Florian

[Fabrizio Giudici]

Florian Brunner wrote:

> Fabrizio Giudici schrieb:
>> Florian Brunner wrote:
>>> Thanks for the link. It seems it's quite recently under discussion:
>>> http://wiki.netbeans.org/PageInfo.jsp?page=MavenizingNbbuildProsAndCons
>>>
>> Indeed, there's an impact to the release cycle. I've seen it (and
>> perhaps resolved) on my projects, figure out what's the impact on a
>> large project such as NetBeans. I'm not saying it can't be done, of
>> course: I'm saying that it needs some deep investigation by the NB
>> guys before deciding.
>>
>> In any case, this is probably the most annoying bug:
>>
>> - maven-release-plugin support for Mercurial may be poor. (mkleint:
>> Agreed. The way release plugin works with svn is not easily
>> transplantable to hg. For each release it creates a new branch/tag,
>> effectively copying the sources. In hg world it would mean forking a
>> new clone. and there's no way to branch/tag just part of the hg
>> repository. So each module's release could trigger new tag/branch on
>> the whole repo (tag probably cheaper) For more, See Versions section
>> below)
>>
>> It's a stupid thing that Maven does - at each release the whole hg
>> repository is cloned *from the remote repository*, and you figure out
>> that NetBeans repo is 1.5GB.
>>
>
> Maybe someone can file an issue to Maven then? Or maybe even provide a
> patch?
>

AFAIK the issue has been filed, unfortunately the fix seems hard,
according to the answers Maven developers gave. Unfortunately I don't
have the URL of the issue at hand.

--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog
Fabrizio.Giudici@... - mobile: [phone]