You are viewing a plain text version of this content. The canonical link for it is here.
Posted to easyant-dev@incubator.apache.org by Nicolas Lalevée <ni...@hibnet.org> on 2012/06/30 11:46:02 UTC

Let's do it

Hi guys,

I was starting to write the report for this month and I felt a little embarrassed. Since the last report, April, there was actually no commit checked in. There was some work, which led to have a bug reported and fixed in Ant.

So guys, let's do it. Let's focus on doing a release. Let's make some effort to keep things going. This low activity is probably affecting everyone motivation.

I think there is cool things ahead. I have being plying with Xtext and I have made a DSL for Ant [1]. We probably should discuss at some point if it would be interesting to have a DSL for Easyant.

But that's ahead. Let's get things rolling. Let's focus on doing a release.
Let's do it !

Nicolas

[1] http://svn.apache.org/repos/asf/ant/sandbox/antdsl/doc/index.html

Re: Grant access to Jenkins

Posted by Nicolas Lalevée <ni...@hibnet.org>.
Le 12 juil. 2012 à 22:40, Jean-Louis Boudart a écrit :

> Should be fixed now, i have backported the code doing target injection into
> extensionPoint until we take a real decision.
> 
> PS: Nicolas i have no access to jenkins configuration or even "build"
> feature on builds.apache.org, could you give me access ? or tell me the
> procedure to get access

I seems we "just" need to add you to the group "hudson-jobadmin". (see the comment on [1]).
I don't know who could be a PMC chair in a podling. Mentors, could you do that ?

Nicolas

[1] https://issues.apache.org/jira/browse/INFRA-4480


> 
> Thanks in advance
> Le 12 juil. 2012 16:19, "Jean-Louis Boudart" <je...@gmail.com>
> a écrit :
> 
>> I think i found the original issue.
>> 
>> Injection of target into ExtensionPoint is deffered by Ant and done at the
>> end of the parsing of the "root" buildfile.
>> 
>> In EasyAnt we create this "root" buildfile by api [1], so we never enter
>> in the if condition [2] responsible of injection of target into
>> extensionPoint.
>> 
>> We introduced this workaround to emulate a "root" buildfile as ant's
>> ImportTask make somes checks to verify we have at least one root level.
>> 
>> I don't know yet what is the best way to clean this i see the following
>> options :
>> 
>>   - Ask ant to extract the target injection to a public method
>>   - Refactor our code to not emulate a "root" buildfile
>> 
>> Any opinions ?
>> 
>> [1]
>> http://svn.apache.org/viewvc/incubator/easyant/core/trunk/src/main/java/org/apache/easyant/core/EasyAntEngine.java?view=markup==> line 451 to 453
>> [2]
>> http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/helper/ProjectHelper2.java?view=markup==> line 175
>> [3]
>> http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/ImportTask.java?view=markup==> line 147
>> 
>> 
>> 2012/7/11 Nicolas Lalevée <ni...@hibnet.org>
>> 
>>> There was some issues with the jenkins too. But now it is back on track
>>> and the build still fails yes.
>>> 
>>> Nicolas
>>> 
>>> Le 11 juil. 2012 à 09:12, Jean-Louis Boudart a écrit :
>>> 
>>>> Sorry for the noise i reproduce the pb now. I have no idea yet about the
>>>> cause.
>>>> Le 7 juil. 2012 13:09, "Jean-Louis Boudart" <
>>> jeanlouis.boudart@gmail.com> a
>>>> écrit :
>>>> 
>>>>> Hum, i tried on another computer having no cache and i have no problem.
>>>>> Can someone confirm ?
>>>>> 
>>>>> 2012/7/4 Jean-Louis Boudart <je...@gmail.com>
>>>>> 
>>>>>> Just commited the configuration to point to online repository.
>>>>>> Artifacts are correclty downloaded from there.
>>>>>> 
>>>>>> Unfortunatly, i can't build easyant itself with build-std-plugin 0.9
>>> as
>>>>>> the build fail with following error :
>>>>>> 
>>>>>> Manifest file: /path/to/easyant-core/target/MANIFEST.MF does not
>>> exist.
>>>>>> 
>>>>>> While scrolling the log i can see that manifest plugin is not
>>> triggered
>>>>>> correctly.
>>>>>> 
>>>>>> Problems seems to come from the buildtype itself, it's a wiring
>>> issue. I
>>>>>> haven't identified yet the problem but i assume it comes from this :
>>>>>> <bindtargets
>>>>>> 
>>> targets="compile-java:compile,manifest:manifest,manifest:manifest-runnable,resources-std:copy-resources"
>>>>>> extensionPoint="package-jar:jar-ready" />
>>>>>> 
>>>>>> I will try to fix this tomorrow.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 2012/7/2 Jean-Louis Boudart <je...@gmail.com>
>>>>>> 
>>>>>>> Hi Nicolas,
>>>>>>> 
>>>>>>> I fully agree with you on the release. You're right this low
>>> activity is
>>>>>>> for sure affecting everyone's motivation.
>>>>>>> I still believe we have cool things to do with this project.
>>>>>>> 
>>>>>>> I should commit a fix on easyant-core/trunk to be able to build the
>>>>>>> project. To clarify the situation :
>>>>>>> 
>>>>>>> As mentioned in an earlier thread plugins/buildtypes will be
>>> published
>>>>>>> on repository.easyant.org. The fix will configure easyant to be
>>> aware
>>>>>>> of this repository.
>>>>>>> The repository[1] currently contains plugins from
>>> easyant/plugins/trunk.
>>>>>>> Thoses plugins may change as they are not really released yet. I will
>>>>>>> publish all trunk easyant/buildtypes there in the same repository.
>>>>>>> 
>>>>>>> You can browse the repository to see how things gets structured (i
>>> will
>>>>>>> open and email to suggest how we could manage it).
>>>>>>> 
>>>>>>> Then, the project would be "buildable" again based on the new
>>>>>>> infrastructure, and we could follow the remaining steps to make the
>>> release.
>>>>>>> 
>>>>>>> I saw your announce about Xtext implementation and it perfectly fill
>>> in
>>>>>>> easyant as we were planning to support "multi language" support for
>>> writing
>>>>>>> easyant plugins.
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> [1] http://repository.easyant.org/
>>>>>>> 
>>>>>>> 
>>>>>>> 2012/6/30 Nicolas Lalevée <ni...@hibnet.org>
>>>>>>> 
>>>>>>>> Hi guys,
>>>>>>>> 
>>>>>>>> I was starting to write the report for this month and I felt a
>>> little
>>>>>>>> embarrassed. Since the last report, April, there was actually no
>>> commit
>>>>>>>> checked in. There was some work, which led to have a bug reported
>>> and fixed
>>>>>>>> in Ant.
>>>>>>>> 
>>>>>>>> So guys, let's do it. Let's focus on doing a release. Let's make
>>> some
>>>>>>>> effort to keep things going. This low activity is probably affecting
>>>>>>>> everyone motivation.
>>>>>>>> 
>>>>>>>> I think there is cool things ahead. I have being plying with Xtext
>>> and
>>>>>>>> I have made a DSL for Ant [1]. We probably should discuss at some
>>> point if
>>>>>>>> it would be interesting to have a DSL for Easyant.
>>>>>>>> 
>>>>>>>> But that's ahead. Let's get things rolling. Let's focus on doing a
>>>>>>>> release.
>>>>>>>> Let's do it !
>>>>>>>> 
>>>>>>>> Nicolas
>>>>>>>> 
>>>>>>>> [1]
>>> http://svn.apache.org/repos/asf/ant/sandbox/antdsl/doc/index.html
>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> --
>>>>>>> Jean Louis Boudart
>>>>>>> Independent consultant
>>>>>>> Apache EasyAnt commiter http://incubator.apache.org/easyant/
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> Jean Louis Boudart
>>>>>> Independent consultant
>>>>>> Apache EasyAnt commiter http://incubator.apache.org/easyant/
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Jean Louis Boudart
>>>>> Independent consultant
>>>>> Apache EasyAnt commiter http://incubator.apache.org/easyant/
>>>>> 
>>> 
>>> 
>> 
>> 
>> --
>> Jean Louis Boudart
>> Independent consultant
>> Apache EasyAnt commiter http://incubator.apache.org/easyant/
>>

Re: Let's do it

Posted by Jean-Louis Boudart <je...@gmail.com>.
Should be fixed now, i have backported the code doing target injection into
extensionPoint until we take a real decision.

PS: Nicolas i have no access to jenkins configuration or even "build"
feature on builds.apache.org, could you give me access ? or tell me the
procedure to get access

Thanks in advance
Le 12 juil. 2012 16:19, "Jean-Louis Boudart" <je...@gmail.com>
a écrit :

> I think i found the original issue.
>
> Injection of target into ExtensionPoint is deffered by Ant and done at the
> end of the parsing of the "root" buildfile.
>
> In EasyAnt we create this "root" buildfile by api [1], so we never enter
> in the if condition [2] responsible of injection of target into
> extensionPoint.
>
> We introduced this workaround to emulate a "root" buildfile as ant's
> ImportTask make somes checks to verify we have at least one root level.
>
> I don't know yet what is the best way to clean this i see the following
> options :
>
>    - Ask ant to extract the target injection to a public method
>    - Refactor our code to not emulate a "root" buildfile
>
> Any opinions ?
>
> [1]
> http://svn.apache.org/viewvc/incubator/easyant/core/trunk/src/main/java/org/apache/easyant/core/EasyAntEngine.java?view=markup==> line 451 to 453
> [2]
> http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/helper/ProjectHelper2.java?view=markup==> line 175
> [3]
> http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/ImportTask.java?view=markup==> line 147
>
>
> 2012/7/11 Nicolas Lalevée <ni...@hibnet.org>
>
>> There was some issues with the jenkins too. But now it is back on track
>> and the build still fails yes.
>>
>> Nicolas
>>
>> Le 11 juil. 2012 à 09:12, Jean-Louis Boudart a écrit :
>>
>> > Sorry for the noise i reproduce the pb now. I have no idea yet about the
>> > cause.
>> > Le 7 juil. 2012 13:09, "Jean-Louis Boudart" <
>> jeanlouis.boudart@gmail.com> a
>> > écrit :
>> >
>> >> Hum, i tried on another computer having no cache and i have no problem.
>> >> Can someone confirm ?
>> >>
>> >> 2012/7/4 Jean-Louis Boudart <je...@gmail.com>
>> >>
>> >>> Just commited the configuration to point to online repository.
>> >>> Artifacts are correclty downloaded from there.
>> >>>
>> >>> Unfortunatly, i can't build easyant itself with build-std-plugin 0.9
>> as
>> >>> the build fail with following error :
>> >>>
>> >>> Manifest file: /path/to/easyant-core/target/MANIFEST.MF does not
>> exist.
>> >>>
>> >>> While scrolling the log i can see that manifest plugin is not
>> triggered
>> >>> correctly.
>> >>>
>> >>> Problems seems to come from the buildtype itself, it's a wiring
>> issue. I
>> >>> haven't identified yet the problem but i assume it comes from this :
>> >>> <bindtargets
>> >>>
>> targets="compile-java:compile,manifest:manifest,manifest:manifest-runnable,resources-std:copy-resources"
>> >>> extensionPoint="package-jar:jar-ready" />
>> >>>
>> >>> I will try to fix this tomorrow.
>> >>>
>> >>>
>> >>>
>> >>> 2012/7/2 Jean-Louis Boudart <je...@gmail.com>
>> >>>
>> >>>> Hi Nicolas,
>> >>>>
>> >>>> I fully agree with you on the release. You're right this low
>> activity is
>> >>>> for sure affecting everyone's motivation.
>> >>>> I still believe we have cool things to do with this project.
>> >>>>
>> >>>> I should commit a fix on easyant-core/trunk to be able to build the
>> >>>> project. To clarify the situation :
>> >>>>
>> >>>> As mentioned in an earlier thread plugins/buildtypes will be
>> published
>> >>>> on repository.easyant.org. The fix will configure easyant to be
>> aware
>> >>>> of this repository.
>> >>>> The repository[1] currently contains plugins from
>> easyant/plugins/trunk.
>> >>>> Thoses plugins may change as they are not really released yet. I will
>> >>>> publish all trunk easyant/buildtypes there in the same repository.
>> >>>>
>> >>>> You can browse the repository to see how things gets structured (i
>> will
>> >>>> open and email to suggest how we could manage it).
>> >>>>
>> >>>> Then, the project would be "buildable" again based on the new
>> >>>> infrastructure, and we could follow the remaining steps to make the
>> release.
>> >>>>
>> >>>> I saw your announce about Xtext implementation and it perfectly fill
>> in
>> >>>> easyant as we were planning to support "multi language" support for
>> writing
>> >>>> easyant plugins.
>> >>>>
>> >>>>
>> >>>>
>> >>>> [1] http://repository.easyant.org/
>> >>>>
>> >>>>
>> >>>> 2012/6/30 Nicolas Lalevée <ni...@hibnet.org>
>> >>>>
>> >>>>> Hi guys,
>> >>>>>
>> >>>>> I was starting to write the report for this month and I felt a
>> little
>> >>>>> embarrassed. Since the last report, April, there was actually no
>> commit
>> >>>>> checked in. There was some work, which led to have a bug reported
>> and fixed
>> >>>>> in Ant.
>> >>>>>
>> >>>>> So guys, let's do it. Let's focus on doing a release. Let's make
>> some
>> >>>>> effort to keep things going. This low activity is probably affecting
>> >>>>> everyone motivation.
>> >>>>>
>> >>>>> I think there is cool things ahead. I have being plying with Xtext
>> and
>> >>>>> I have made a DSL for Ant [1]. We probably should discuss at some
>> point if
>> >>>>> it would be interesting to have a DSL for Easyant.
>> >>>>>
>> >>>>> But that's ahead. Let's get things rolling. Let's focus on doing a
>> >>>>> release.
>> >>>>> Let's do it !
>> >>>>>
>> >>>>> Nicolas
>> >>>>>
>> >>>>> [1]
>> http://svn.apache.org/repos/asf/ant/sandbox/antdsl/doc/index.html
>> >>>>>
>> >>>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Jean Louis Boudart
>> >>>> Independent consultant
>> >>>> Apache EasyAnt commiter http://incubator.apache.org/easyant/
>> >>>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Jean Louis Boudart
>> >>> Independent consultant
>> >>> Apache EasyAnt commiter http://incubator.apache.org/easyant/
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Jean Louis Boudart
>> >> Independent consultant
>> >> Apache EasyAnt commiter http://incubator.apache.org/easyant/
>> >>
>>
>>
>
>
> --
> Jean Louis Boudart
> Independent consultant
> Apache EasyAnt commiter http://incubator.apache.org/easyant/
>

Re: Let's do it

Posted by Jean-Louis Boudart <je...@gmail.com>.
I think i found the original issue.

Injection of target into ExtensionPoint is deffered by Ant and done at the
end of the parsing of the "root" buildfile.

In EasyAnt we create this "root" buildfile by api [1], so we never enter in
the if condition [2] responsible of injection of target into extensionPoint.

We introduced this workaround to emulate a "root" buildfile as ant's
ImportTask make somes checks to verify we have at least one root level.

I don't know yet what is the best way to clean this i see the following
options :

   - Ask ant to extract the target injection to a public method
   - Refactor our code to not emulate a "root" buildfile

Any opinions ?

[1]
http://svn.apache.org/viewvc/incubator/easyant/core/trunk/src/main/java/org/apache/easyant/core/EasyAntEngine.java?view=markup==>
line 451 to 453
[2]
http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/helper/ProjectHelper2.java?view=markup==>
line 175
[3]
http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/ImportTask.java?view=markup==>
line 147


2012/7/11 Nicolas Lalevée <ni...@hibnet.org>

> There was some issues with the jenkins too. But now it is back on track
> and the build still fails yes.
>
> Nicolas
>
> Le 11 juil. 2012 à 09:12, Jean-Louis Boudart a écrit :
>
> > Sorry for the noise i reproduce the pb now. I have no idea yet about the
> > cause.
> > Le 7 juil. 2012 13:09, "Jean-Louis Boudart" <je...@gmail.com>
> a
> > écrit :
> >
> >> Hum, i tried on another computer having no cache and i have no problem.
> >> Can someone confirm ?
> >>
> >> 2012/7/4 Jean-Louis Boudart <je...@gmail.com>
> >>
> >>> Just commited the configuration to point to online repository.
> >>> Artifacts are correclty downloaded from there.
> >>>
> >>> Unfortunatly, i can't build easyant itself with build-std-plugin 0.9 as
> >>> the build fail with following error :
> >>>
> >>> Manifest file: /path/to/easyant-core/target/MANIFEST.MF does not exist.
> >>>
> >>> While scrolling the log i can see that manifest plugin is not triggered
> >>> correctly.
> >>>
> >>> Problems seems to come from the buildtype itself, it's a wiring issue.
> I
> >>> haven't identified yet the problem but i assume it comes from this :
> >>> <bindtargets
> >>>
> targets="compile-java:compile,manifest:manifest,manifest:manifest-runnable,resources-std:copy-resources"
> >>> extensionPoint="package-jar:jar-ready" />
> >>>
> >>> I will try to fix this tomorrow.
> >>>
> >>>
> >>>
> >>> 2012/7/2 Jean-Louis Boudart <je...@gmail.com>
> >>>
> >>>> Hi Nicolas,
> >>>>
> >>>> I fully agree with you on the release. You're right this low activity
> is
> >>>> for sure affecting everyone's motivation.
> >>>> I still believe we have cool things to do with this project.
> >>>>
> >>>> I should commit a fix on easyant-core/trunk to be able to build the
> >>>> project. To clarify the situation :
> >>>>
> >>>> As mentioned in an earlier thread plugins/buildtypes will be published
> >>>> on repository.easyant.org. The fix will configure easyant to be aware
> >>>> of this repository.
> >>>> The repository[1] currently contains plugins from
> easyant/plugins/trunk.
> >>>> Thoses plugins may change as they are not really released yet. I will
> >>>> publish all trunk easyant/buildtypes there in the same repository.
> >>>>
> >>>> You can browse the repository to see how things gets structured (i
> will
> >>>> open and email to suggest how we could manage it).
> >>>>
> >>>> Then, the project would be "buildable" again based on the new
> >>>> infrastructure, and we could follow the remaining steps to make the
> release.
> >>>>
> >>>> I saw your announce about Xtext implementation and it perfectly fill
> in
> >>>> easyant as we were planning to support "multi language" support for
> writing
> >>>> easyant plugins.
> >>>>
> >>>>
> >>>>
> >>>> [1] http://repository.easyant.org/
> >>>>
> >>>>
> >>>> 2012/6/30 Nicolas Lalevée <ni...@hibnet.org>
> >>>>
> >>>>> Hi guys,
> >>>>>
> >>>>> I was starting to write the report for this month and I felt a little
> >>>>> embarrassed. Since the last report, April, there was actually no
> commit
> >>>>> checked in. There was some work, which led to have a bug reported
> and fixed
> >>>>> in Ant.
> >>>>>
> >>>>> So guys, let's do it. Let's focus on doing a release. Let's make some
> >>>>> effort to keep things going. This low activity is probably affecting
> >>>>> everyone motivation.
> >>>>>
> >>>>> I think there is cool things ahead. I have being plying with Xtext
> and
> >>>>> I have made a DSL for Ant [1]. We probably should discuss at some
> point if
> >>>>> it would be interesting to have a DSL for Easyant.
> >>>>>
> >>>>> But that's ahead. Let's get things rolling. Let's focus on doing a
> >>>>> release.
> >>>>> Let's do it !
> >>>>>
> >>>>> Nicolas
> >>>>>
> >>>>> [1]
> http://svn.apache.org/repos/asf/ant/sandbox/antdsl/doc/index.html
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> Jean Louis Boudart
> >>>> Independent consultant
> >>>> Apache EasyAnt commiter http://incubator.apache.org/easyant/
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Jean Louis Boudart
> >>> Independent consultant
> >>> Apache EasyAnt commiter http://incubator.apache.org/easyant/
> >>>
> >>
> >>
> >>
> >> --
> >> Jean Louis Boudart
> >> Independent consultant
> >> Apache EasyAnt commiter http://incubator.apache.org/easyant/
> >>
>
>


-- 
Jean Louis Boudart
Independent consultant
Apache EasyAnt commiter http://incubator.apache.org/easyant/

Re: Let's do it

Posted by Nicolas Lalevée <ni...@hibnet.org>.
There was some issues with the jenkins too. But now it is back on track and the build still fails yes.

Nicolas

Le 11 juil. 2012 à 09:12, Jean-Louis Boudart a écrit :

> Sorry for the noise i reproduce the pb now. I have no idea yet about the
> cause.
> Le 7 juil. 2012 13:09, "Jean-Louis Boudart" <je...@gmail.com> a
> écrit :
> 
>> Hum, i tried on another computer having no cache and i have no problem.
>> Can someone confirm ?
>> 
>> 2012/7/4 Jean-Louis Boudart <je...@gmail.com>
>> 
>>> Just commited the configuration to point to online repository.
>>> Artifacts are correclty downloaded from there.
>>> 
>>> Unfortunatly, i can't build easyant itself with build-std-plugin 0.9 as
>>> the build fail with following error :
>>> 
>>> Manifest file: /path/to/easyant-core/target/MANIFEST.MF does not exist.
>>> 
>>> While scrolling the log i can see that manifest plugin is not triggered
>>> correctly.
>>> 
>>> Problems seems to come from the buildtype itself, it's a wiring issue. I
>>> haven't identified yet the problem but i assume it comes from this :
>>> <bindtargets
>>> targets="compile-java:compile,manifest:manifest,manifest:manifest-runnable,resources-std:copy-resources"
>>> extensionPoint="package-jar:jar-ready" />
>>> 
>>> I will try to fix this tomorrow.
>>> 
>>> 
>>> 
>>> 2012/7/2 Jean-Louis Boudart <je...@gmail.com>
>>> 
>>>> Hi Nicolas,
>>>> 
>>>> I fully agree with you on the release. You're right this low activity is
>>>> for sure affecting everyone's motivation.
>>>> I still believe we have cool things to do with this project.
>>>> 
>>>> I should commit a fix on easyant-core/trunk to be able to build the
>>>> project. To clarify the situation :
>>>> 
>>>> As mentioned in an earlier thread plugins/buildtypes will be published
>>>> on repository.easyant.org. The fix will configure easyant to be aware
>>>> of this repository.
>>>> The repository[1] currently contains plugins from easyant/plugins/trunk.
>>>> Thoses plugins may change as they are not really released yet. I will
>>>> publish all trunk easyant/buildtypes there in the same repository.
>>>> 
>>>> You can browse the repository to see how things gets structured (i will
>>>> open and email to suggest how we could manage it).
>>>> 
>>>> Then, the project would be "buildable" again based on the new
>>>> infrastructure, and we could follow the remaining steps to make the release.
>>>> 
>>>> I saw your announce about Xtext implementation and it perfectly fill in
>>>> easyant as we were planning to support "multi language" support for writing
>>>> easyant plugins.
>>>> 
>>>> 
>>>> 
>>>> [1] http://repository.easyant.org/
>>>> 
>>>> 
>>>> 2012/6/30 Nicolas Lalevée <ni...@hibnet.org>
>>>> 
>>>>> Hi guys,
>>>>> 
>>>>> I was starting to write the report for this month and I felt a little
>>>>> embarrassed. Since the last report, April, there was actually no commit
>>>>> checked in. There was some work, which led to have a bug reported and fixed
>>>>> in Ant.
>>>>> 
>>>>> So guys, let's do it. Let's focus on doing a release. Let's make some
>>>>> effort to keep things going. This low activity is probably affecting
>>>>> everyone motivation.
>>>>> 
>>>>> I think there is cool things ahead. I have being plying with Xtext and
>>>>> I have made a DSL for Ant [1]. We probably should discuss at some point if
>>>>> it would be interesting to have a DSL for Easyant.
>>>>> 
>>>>> But that's ahead. Let's get things rolling. Let's focus on doing a
>>>>> release.
>>>>> Let's do it !
>>>>> 
>>>>> Nicolas
>>>>> 
>>>>> [1] http://svn.apache.org/repos/asf/ant/sandbox/antdsl/doc/index.html
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> --
>>>> Jean Louis Boudart
>>>> Independent consultant
>>>> Apache EasyAnt commiter http://incubator.apache.org/easyant/
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> Jean Louis Boudart
>>> Independent consultant
>>> Apache EasyAnt commiter http://incubator.apache.org/easyant/
>>> 
>> 
>> 
>> 
>> --
>> Jean Louis Boudart
>> Independent consultant
>> Apache EasyAnt commiter http://incubator.apache.org/easyant/
>>

Re: Let's do it

Posted by Jean-Louis Boudart <je...@gmail.com>.
Sorry for the noise i reproduce the pb now. I have no idea yet about the
cause.
Le 7 juil. 2012 13:09, "Jean-Louis Boudart" <je...@gmail.com> a
écrit :

> Hum, i tried on another computer having no cache and i have no problem.
> Can someone confirm ?
>
> 2012/7/4 Jean-Louis Boudart <je...@gmail.com>
>
>> Just commited the configuration to point to online repository.
>> Artifacts are correclty downloaded from there.
>>
>> Unfortunatly, i can't build easyant itself with build-std-plugin 0.9 as
>> the build fail with following error :
>>
>>  Manifest file: /path/to/easyant-core/target/MANIFEST.MF does not exist.
>>
>> While scrolling the log i can see that manifest plugin is not triggered
>> correctly.
>>
>> Problems seems to come from the buildtype itself, it's a wiring issue. I
>> haven't identified yet the problem but i assume it comes from this :
>> <bindtargets
>> targets="compile-java:compile,manifest:manifest,manifest:manifest-runnable,resources-std:copy-resources"
>> extensionPoint="package-jar:jar-ready" />
>>
>> I will try to fix this tomorrow.
>>
>>
>>
>> 2012/7/2 Jean-Louis Boudart <je...@gmail.com>
>>
>>> Hi Nicolas,
>>>
>>> I fully agree with you on the release. You're right this low activity is
>>> for sure affecting everyone's motivation.
>>> I still believe we have cool things to do with this project.
>>>
>>> I should commit a fix on easyant-core/trunk to be able to build the
>>> project. To clarify the situation :
>>>
>>> As mentioned in an earlier thread plugins/buildtypes will be published
>>> on repository.easyant.org. The fix will configure easyant to be aware
>>> of this repository.
>>> The repository[1] currently contains plugins from easyant/plugins/trunk.
>>> Thoses plugins may change as they are not really released yet. I will
>>> publish all trunk easyant/buildtypes there in the same repository.
>>>
>>> You can browse the repository to see how things gets structured (i will
>>> open and email to suggest how we could manage it).
>>>
>>> Then, the project would be "buildable" again based on the new
>>> infrastructure, and we could follow the remaining steps to make the release.
>>>
>>> I saw your announce about Xtext implementation and it perfectly fill in
>>> easyant as we were planning to support "multi language" support for writing
>>> easyant plugins.
>>>
>>>
>>>
>>> [1] http://repository.easyant.org/
>>>
>>>
>>> 2012/6/30 Nicolas Lalevée <ni...@hibnet.org>
>>>
>>>> Hi guys,
>>>>
>>>> I was starting to write the report for this month and I felt a little
>>>> embarrassed. Since the last report, April, there was actually no commit
>>>> checked in. There was some work, which led to have a bug reported and fixed
>>>> in Ant.
>>>>
>>>> So guys, let's do it. Let's focus on doing a release. Let's make some
>>>> effort to keep things going. This low activity is probably affecting
>>>> everyone motivation.
>>>>
>>>> I think there is cool things ahead. I have being plying with Xtext and
>>>> I have made a DSL for Ant [1]. We probably should discuss at some point if
>>>> it would be interesting to have a DSL for Easyant.
>>>>
>>>> But that's ahead. Let's get things rolling. Let's focus on doing a
>>>> release.
>>>> Let's do it !
>>>>
>>>> Nicolas
>>>>
>>>> [1] http://svn.apache.org/repos/asf/ant/sandbox/antdsl/doc/index.html
>>>>
>>>>
>>>
>>>
>>> --
>>> Jean Louis Boudart
>>> Independent consultant
>>> Apache EasyAnt commiter http://incubator.apache.org/easyant/
>>>
>>
>>
>>
>> --
>> Jean Louis Boudart
>> Independent consultant
>> Apache EasyAnt commiter http://incubator.apache.org/easyant/
>>
>
>
>
> --
> Jean Louis Boudart
> Independent consultant
> Apache EasyAnt commiter http://incubator.apache.org/easyant/
>

Re: Let's do it

Posted by Jean-Louis Boudart <je...@gmail.com>.
Hum, i tried on another computer having no cache and i have no problem.
Can someone confirm ?

2012/7/4 Jean-Louis Boudart <je...@gmail.com>

> Just commited the configuration to point to online repository.
> Artifacts are correclty downloaded from there.
>
> Unfortunatly, i can't build easyant itself with build-std-plugin 0.9 as
> the build fail with following error :
>
>  Manifest file: /path/to/easyant-core/target/MANIFEST.MF does not exist.
>
> While scrolling the log i can see that manifest plugin is not triggered
> correctly.
>
> Problems seems to come from the buildtype itself, it's a wiring issue. I
> haven't identified yet the problem but i assume it comes from this :
> <bindtargets
> targets="compile-java:compile,manifest:manifest,manifest:manifest-runnable,resources-std:copy-resources"
> extensionPoint="package-jar:jar-ready" />
>
> I will try to fix this tomorrow.
>
>
>
> 2012/7/2 Jean-Louis Boudart <je...@gmail.com>
>
>> Hi Nicolas,
>>
>> I fully agree with you on the release. You're right this low activity is
>> for sure affecting everyone's motivation.
>> I still believe we have cool things to do with this project.
>>
>> I should commit a fix on easyant-core/trunk to be able to build the
>> project. To clarify the situation :
>>
>> As mentioned in an earlier thread plugins/buildtypes will be published on
>> repository.easyant.org. The fix will configure easyant to be aware of
>> this repository.
>> The repository[1] currently contains plugins from easyant/plugins/trunk.
>> Thoses plugins may change as they are not really released yet. I will
>> publish all trunk easyant/buildtypes there in the same repository.
>>
>> You can browse the repository to see how things gets structured (i will
>> open and email to suggest how we could manage it).
>>
>> Then, the project would be "buildable" again based on the new
>> infrastructure, and we could follow the remaining steps to make the release.
>>
>> I saw your announce about Xtext implementation and it perfectly fill in
>> easyant as we were planning to support "multi language" support for writing
>> easyant plugins.
>>
>>
>>
>> [1] http://repository.easyant.org/
>>
>>
>> 2012/6/30 Nicolas Lalevée <ni...@hibnet.org>
>>
>>> Hi guys,
>>>
>>> I was starting to write the report for this month and I felt a little
>>> embarrassed. Since the last report, April, there was actually no commit
>>> checked in. There was some work, which led to have a bug reported and fixed
>>> in Ant.
>>>
>>> So guys, let's do it. Let's focus on doing a release. Let's make some
>>> effort to keep things going. This low activity is probably affecting
>>> everyone motivation.
>>>
>>> I think there is cool things ahead. I have being plying with Xtext and I
>>> have made a DSL for Ant [1]. We probably should discuss at some point if it
>>> would be interesting to have a DSL for Easyant.
>>>
>>> But that's ahead. Let's get things rolling. Let's focus on doing a
>>> release.
>>> Let's do it !
>>>
>>> Nicolas
>>>
>>> [1] http://svn.apache.org/repos/asf/ant/sandbox/antdsl/doc/index.html
>>>
>>>
>>
>>
>> --
>> Jean Louis Boudart
>> Independent consultant
>> Apache EasyAnt commiter http://incubator.apache.org/easyant/
>>
>
>
>
> --
> Jean Louis Boudart
> Independent consultant
> Apache EasyAnt commiter http://incubator.apache.org/easyant/
>



-- 
Jean Louis Boudart
Independent consultant
Apache EasyAnt commiter http://incubator.apache.org/easyant/

Re: Let's do it

Posted by Jean-Louis Boudart <je...@gmail.com>.
Just commited the configuration to point to online repository.
Artifacts are correclty downloaded from there.

Unfortunatly, i can't build easyant itself with build-std-plugin 0.9 as the
build fail with following error :

 Manifest file: /path/to/easyant-core/target/MANIFEST.MF does not exist.

While scrolling the log i can see that manifest plugin is not triggered
correctly.

Problems seems to come from the buildtype itself, it's a wiring issue. I
haven't identified yet the problem but i assume it comes from this :
<bindtargets
targets="compile-java:compile,manifest:manifest,manifest:manifest-runnable,resources-std:copy-resources"
extensionPoint="package-jar:jar-ready" />

I will try to fix this tomorrow.



2012/7/2 Jean-Louis Boudart <je...@gmail.com>

> Hi Nicolas,
>
> I fully agree with you on the release. You're right this low activity is
> for sure affecting everyone's motivation.
> I still believe we have cool things to do with this project.
>
> I should commit a fix on easyant-core/trunk to be able to build the
> project. To clarify the situation :
>
> As mentioned in an earlier thread plugins/buildtypes will be published on
> repository.easyant.org. The fix will configure easyant to be aware of
> this repository.
> The repository[1] currently contains plugins from easyant/plugins/trunk.
> Thoses plugins may change as they are not really released yet. I will
> publish all trunk easyant/buildtypes there in the same repository.
>
> You can browse the repository to see how things gets structured (i will
> open and email to suggest how we could manage it).
>
> Then, the project would be "buildable" again based on the new
> infrastructure, and we could follow the remaining steps to make the release.
>
> I saw your announce about Xtext implementation and it perfectly fill in
> easyant as we were planning to support "multi language" support for writing
> easyant plugins.
>
>
>
> [1] http://repository.easyant.org/
>
>
> 2012/6/30 Nicolas Lalevée <ni...@hibnet.org>
>
>> Hi guys,
>>
>> I was starting to write the report for this month and I felt a little
>> embarrassed. Since the last report, April, there was actually no commit
>> checked in. There was some work, which led to have a bug reported and fixed
>> in Ant.
>>
>> So guys, let's do it. Let's focus on doing a release. Let's make some
>> effort to keep things going. This low activity is probably affecting
>> everyone motivation.
>>
>> I think there is cool things ahead. I have being plying with Xtext and I
>> have made a DSL for Ant [1]. We probably should discuss at some point if it
>> would be interesting to have a DSL for Easyant.
>>
>> But that's ahead. Let's get things rolling. Let's focus on doing a
>> release.
>> Let's do it !
>>
>> Nicolas
>>
>> [1] http://svn.apache.org/repos/asf/ant/sandbox/antdsl/doc/index.html
>>
>>
>
>
> --
> Jean Louis Boudart
> Independent consultant
> Apache EasyAnt commiter http://incubator.apache.org/easyant/
>



-- 
Jean Louis Boudart
Independent consultant
Apache EasyAnt commiter http://incubator.apache.org/easyant/

Re: Let's do it

Posted by Jean-Louis Boudart <je...@gmail.com>.
Hi Nicolas,

I fully agree with you on the release. You're right this low activity is
for sure affecting everyone's motivation.
I still believe we have cool things to do with this project.

I should commit a fix on easyant-core/trunk to be able to build the
project. To clarify the situation :

As mentioned in an earlier thread plugins/buildtypes will be published on
repository.easyant.org. The fix will configure easyant to be aware of this
repository.
The repository[1] currently contains plugins from easyant/plugins/trunk.
Thoses plugins may change as they are not really released yet. I will
publish all trunk easyant/buildtypes there in the same repository.

You can browse the repository to see how things gets structured (i will
open and email to suggest how we could manage it).

Then, the project would be "buildable" again based on the new
infrastructure, and we could follow the remaining steps to make the release.

I saw your announce about Xtext implementation and it perfectly fill in
easyant as we were planning to support "multi language" support for writing
easyant plugins.



[1] http://repository.easyant.org/

2012/6/30 Nicolas Lalevée <ni...@hibnet.org>

> Hi guys,
>
> I was starting to write the report for this month and I felt a little
> embarrassed. Since the last report, April, there was actually no commit
> checked in. There was some work, which led to have a bug reported and fixed
> in Ant.
>
> So guys, let's do it. Let's focus on doing a release. Let's make some
> effort to keep things going. This low activity is probably affecting
> everyone motivation.
>
> I think there is cool things ahead. I have being plying with Xtext and I
> have made a DSL for Ant [1]. We probably should discuss at some point if it
> would be interesting to have a DSL for Easyant.
>
> But that's ahead. Let's get things rolling. Let's focus on doing a release.
> Let's do it !
>
> Nicolas
>
> [1] http://svn.apache.org/repos/asf/ant/sandbox/antdsl/doc/index.html
>
>


-- 
Jean Louis Boudart
Independent consultant
Apache EasyAnt commiter http://incubator.apache.org/easyant/