Re: target-group committed

[Stefan Bodewig]

On 2008-11-28, Jean-Louis BOUDART <[EMAIL PROTECTED]> wrote:

> Any news on this point?

I've still not seen any argument that convinced me that the naming
rules for  should be different, but that's just me.

On the target-group as composite side, I may start to understand it,
but feel that we've been tackling the wrong way.  Instead of madifying
depends, target-group should have a parts attribute that targets can
append to.  Or something like that.

I haven't made up my mind on any of this.  But like I said, it is just
me, don't wait for me.

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: target-group committed

[Jean-Louis BOUDART]

Any news on this point?

2008/11/24 Xavier Hanin <[EMAIL PROTECTED]>

> On Fri, Nov 21, 2008 at 12:26 AM, Jean-Louis BOUDART <
> [EMAIL PROTECTED]> wrote:
>
> > >
> > > > In addition, as we use target-group to have more "genericity" we
> > doesn't
> > > > want to have prefix on those "generic" targets.
> > >
> > > I'm afraid I don't understand this.
> > >
> > > One of your selling points for  was that the included build is
> > > self-contained and remains that way by prefixing all traget names and
> > > rewriting the depends lists.
> > >
> > > If we break that rule for some kind of target, the included build is
> > > suddenly open for modifications from the outside - including overrides
> > > of target-groups.
> > >
> > Again if we consider target-group as JUST a way to have target dependency
> > injection, this doesn't make sens.
> > In opposite if we consider that target-groups are toplevel target does't
> it
> > make sens to have prefix on target-group?
> > Example (using current HEAD revision):
> > Suppose you want to have a generic task called report
> > a.xml
> > 
> > 
> > javadoc
> > 
> > ...
> > 
> >
> > b.xml
> > 
> > 
> > junitreport
> > 
> > ...
> > 
> >
> > c.xml
> > 
> >  > target-group="report">
> >  emma report
> > 
> > ...
> > 
> >
> > phases.xml
> > 
> > 
> > 
> >
> > build.xml
> > 
> > 
> > 
> > 
> > 
> > 
> >
> >
> > If you try to use "ant report" :
> > you have this message
> > "can't add target javadoc.javadoc to target-group javadoc.report because
> > the
> > target-group is unknown."
> >
> > IMHO a target-group should NEVER be prefixed, in a module it's possible
> to
> > assign a target to a phase which is not declared in the build module. It
> > makes the module dependent on the caller to declare the phase prior to
> the
> > use call, and as such becomes a requirement of the module.
> >
> >
> I would like to bring more attention to this, because I think Jean-Louis
> makes a very good point here.
> IMO joining a target group for a target should be possible for a target
> group which is defined in a build file "including" the build file in which
> the target itself is defined.
>
> So maybe name resolution of a target-group when a target declares to join a
> target-group (with ) in an included
> file should first look for the prefixed name (as it is currently
> implemented) and then if it doesn't exist, try to look for the non prefixed
> name.
>
> WDYT?
>
> --
> Xavier Hanin - 4SH France
> BordeauxJUG co leader - http://www.bordeauxjug.org/
> Blogger - http://xhab.blogspot.com/
> Apache Ivy Creator - http://ant.apache.org/ivy/
>

Re: target-group committed

[Jean-Louis BOUDART]

I'm +1 for this solution
2008/11/26 Dominique Devienne <[EMAIL PROTECTED]>

> On Wed, Nov 26, 2008 at 2:06 PM, Bruce Atherton <[EMAIL PROTECTED]>
> wrote:
> > Or you could just live with the verbosity of the target list, like I did,
> > and use naming conventions in EasyAnt. I'm sure there are many other ways
> to
> > address the issue.
>
> One possible way would be to provide an in-build-file hook to
> intercept the -p switch, and this hook (I envision a target) would
> then be responsible to display the help. Couple that with a new
> configurable task to generate the -p output, and then it's up to the
> user to select (via some kind of include/exclude) whatever targets are
> going to be listed.
>
> My builds used to all have a help target which 'd back into Ant
> on the same build file with the -p switch added. It's the same idea,
> but exposing a builtin task instead, and allowing to run that target
> when -p is specified, if it's hooked via for example a  help-target="help">.
>
> --DD
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Updating the Continuous/Synergy tasks that are shipped with Ant

[Dave]

I can see your point. Perhaps Apache could approach IBM about a free license
for the tool just for such a purpose.Its much better for IBM if Ant has
well-integrated Synergy support.

On Fri, Nov 28, 2008 at 12:46 PM, <[EMAIL PROTECTED]> wrote:

> What we need is an automatic unit test.
> This requires a testbed.
>
> As an AntLib for a very special scm we could live with the fact that not
> any committer has access to the scm system. But a few should have. And they
> should have a test suite so they can "click a button and get the result".
>
>
> Jan
>
> >-Ursprüngliche Nachricht-
> >Von: Dave [mailto:[EMAIL PROTECTED]
> >Gesendet: Freitag, 28. November 2008 11:48
> >An: Ant Developers List
> >Betreff: Re: Updating the Continuous/Synergy tasks that are
> >shipped with Ant
> >
> >Well if you'd like to send me your Antlibs, I can do some
> >testing for you
> >here. We're using Synergy 6.5 SP2 (and we're planning on installing the
> >first post-SP2 patch next wednesday). Would that be of interest to you?
> >
> >On Fri, Nov 28, 2008 at 10:39 AM, <[EMAIL PROTECTED]> wrote:
> >
> >> We are using Synergy 6.5 at the moment and using it since
> >... mmh ... 5.1?
> >> 4.5?
> >> With 6.5 Synergy has a Java client (ok present in 6.1 also),
> >but sadly no
> >> real and open "API" so these tasks wrap the command line client.
> >>
> >> As often with scm tasks a test environment for unit tests is
> >difficult ...
> >>
> >>
> >> Jan
> >>
> >>
> >>
> >>
> >>
> >>  >uiDatabaseDir=""
> >> initialRole=""/>
> >> Starts a Synergy session
> >>
> >> 
> >> Stops a Synergy session
> >>
> >> 
> >> Connects to a running session. ("CCM_ADDR" not set by the
> >Java client any
> >> more)
> >>
> >> 
> >>
> >> 
> >> Check files out
> >>
> >> 
> >> Check a project out
> >>  ccm co -p ${project}-${version} -release ${release} -mod
> >-path ${workarea}
> >>
> >> 
> >> Reconfigure command
> >>
> >>  >> asDefault=""/>
> >> Creates a new task
> >>
> >> 
> >>
> >>  >> interfacekind="info.interface"
> >> ip="info.ip"
> >> sessionid="info.session"
> >> user="info.user"
> >> computer="info.computer"/>
> >> 
> >> Gets information about the current session
> >>  [echoproperties] #Ant properties
> >>  [echoproperties] #Mon May 22 09:46:33 CEST 2006
> >>  [echoproperties] info.interface=Command Interface
> >>  [echoproperties] info.user=mat
> >>  [echoproperties] info.session=1707
> >>  [echoproperties] info.ip=130.11.36.89
> >>  [echoproperties] info.db=/rzf/db/skm/ccm_databases/uebungen
> >>  [echoproperties] info.computer=nb011689
> >>
> >> 
> >> 
> >>
> >>
> >>
> >> 
> >> Checks for a give role (task and condition)
> >>
> >> 
> >> Stores the object version of a given file in a property.
> >Optional default
> >> value if not under CM control.
> >>
> >>  >detailed="">
> >> >prefix="https://myJira.org/browse/
> >> "/>
> >> 
> >> Creates a changelist by getting all completed tasks of a release. The
> >> result is a text or xml file with release name and task synopsis. If
> >> "detailed" with their documentations too. A XSL could
> >transform that into
> >> HTML.
> >>  >>in="${build.dir}/changes-detailed.xml"
> >>out="${build.dir}/changes.html"
> >> >
> >>
> >>
> >>
> >> >expression="${release.name}/${release.version}"/>
> >> 
> >>
> >>
> >>
> >> 
> >> 
> >>
> >>
> >> 
> >> Moving with Synergy.
> >>
> >>
> >> 
> >> Checks whether an open Synergy session is available.
> >>
> >>
> >>
> >> >-Ursprüngliche Nachricht-
> >> >Von: Dave [mailto:[EMAIL PROTECTED]
> >> >Gesendet: Freitag, 28. November 2008 10:40
> >> >An: Ant Developers List
> >> >Betreff: Re: Updating the Continuous/Synergy tasks that are
> >> >shipped with Ant
> >> >
> >> >Sounds good. I haven't started working on them yet, but I'd
> >probably be
> >> >enhancing the existing tasks a little (as they're still
> >> >relevant) and adding
> >> >one or two new tasks.I'll post back here once I have
> >something to show.
> >> >Are you also using Synergy at your workplace, or was the antlib for
> >> >something else?
> >> >
> >> >On Fri, Nov 28, 2008 at 7:11 AM, <[EMAIL PROTECTED]> wrote:
> >> >
> >> >> >Hey all,
> >> >> >I'm the build manager working a financial company in Ireland.
> >> >> >I'd like to add some more functionality to the standard
> >> >> >Continuous/ Synergy
> >> >> >tasks which come with Ant.
> >> >> >They're quite old now and could use some updating.
> >> >> >How do I go about contributing source to the Ant project?
> >> >> >Do I need to send svn diff's to the mailing list, or is
> >> >their another
> >> >> >preferred way?
> >> >>
> >> >> I would suggest to deprecate the internal tasks and create a
> >> >new antlib.
> >> >>
> >> >> Do you have some implementations?
> >> >> I have written a new antlib for my company and I can ask for
> >> >> contributing that.
> 

AW: Updating the Continuous/Synergy tasks that are shipped with Ant

[Jan.Materne]

What we need is an automatic unit test.
This requires a testbed.

As an AntLib for a very special scm we could live with the fact that not any 
committer has access to the scm system. But a few should have. And they should 
have a test suite so they can "click a button and get the result".


Jan

>-Ursprüngliche Nachricht-
>Von: Dave [mailto:[EMAIL PROTECTED] 
>Gesendet: Freitag, 28. November 2008 11:48
>An: Ant Developers List
>Betreff: Re: Updating the Continuous/Synergy tasks that are 
>shipped with Ant
>
>Well if you'd like to send me your Antlibs, I can do some 
>testing for you
>here. We're using Synergy 6.5 SP2 (and we're planning on installing the
>first post-SP2 patch next wednesday). Would that be of interest to you?
>
>On Fri, Nov 28, 2008 at 10:39 AM, <[EMAIL PROTECTED]> wrote:
>
>> We are using Synergy 6.5 at the moment and using it since 
>... mmh ... 5.1?
>> 4.5?
>> With 6.5 Synergy has a Java client (ok present in 6.1 also), 
>but sadly no
>> real and open "API" so these tasks wrap the command line client.
>>
>> As often with scm tasks a test environment for unit tests is 
>difficult ...
>>
>>
>> Jan
>>
>>
>>
>>
>>
>> uiDatabaseDir=""
>> initialRole=""/>
>> Starts a Synergy session
>>
>> 
>> Stops a Synergy session
>>
>> 
>> Connects to a running session. ("CCM_ADDR" not set by the 
>Java client any
>> more)
>>
>> 
>>
>> 
>> Check files out
>>
>> 
>> Check a project out
>>  ccm co -p ${project}-${version} -release ${release} -mod 
>-path ${workarea}
>>
>> 
>> Reconfigure command
>>
>> > asDefault=""/>
>> Creates a new task
>>
>> 
>>
>> > interfacekind="info.interface"
>> ip="info.ip"
>> sessionid="info.session"
>> user="info.user"
>> computer="info.computer"/>
>> 
>> Gets information about the current session
>>  [echoproperties] #Ant properties
>>  [echoproperties] #Mon May 22 09:46:33 CEST 2006
>>  [echoproperties] info.interface=Command Interface
>>  [echoproperties] info.user=mat
>>  [echoproperties] info.session=1707
>>  [echoproperties] info.ip=130.11.36.89
>>  [echoproperties] info.db=/rzf/db/skm/ccm_databases/uebungen
>>  [echoproperties] info.computer=nb011689
>>
>> 
>> 
>>
>>
>>
>> 
>> Checks for a give role (task and condition)
>>
>> 
>> Stores the object version of a given file in a property. 
>Optional default
>> value if not under CM control.
>>
>> detailed="">
>>prefix="https://myJira.org/browse/
>> "/>
>> 
>> Creates a changelist by getting all completed tasks of a release. The
>> result is a text or xml file with release name and task synopsis. If
>> "detailed" with their documentations too. A XSL could 
>transform that into
>> HTML.
>> >in="${build.dir}/changes-detailed.xml"
>>out="${build.dir}/changes.html"
>> >
>>
>>
>>
>>expression="${release.name}/${release.version}"/>
>> 
>>
>>
>>
>> 
>> 
>>
>>
>> 
>> Moving with Synergy.
>>
>>
>> 
>> Checks whether an open Synergy session is available.
>>
>>
>>
>> >-Ursprüngliche Nachricht-
>> >Von: Dave [mailto:[EMAIL PROTECTED]
>> >Gesendet: Freitag, 28. November 2008 10:40
>> >An: Ant Developers List
>> >Betreff: Re: Updating the Continuous/Synergy tasks that are
>> >shipped with Ant
>> >
>> >Sounds good. I haven't started working on them yet, but I'd 
>probably be
>> >enhancing the existing tasks a little (as they're still
>> >relevant) and adding
>> >one or two new tasks.I'll post back here once I have 
>something to show.
>> >Are you also using Synergy at your workplace, or was the antlib for
>> >something else?
>> >
>> >On Fri, Nov 28, 2008 at 7:11 AM, <[EMAIL PROTECTED]> wrote:
>> >
>> >> >Hey all,
>> >> >I'm the build manager working a financial company in Ireland.
>> >> >I'd like to add some more functionality to the standard
>> >> >Continuous/ Synergy
>> >> >tasks which come with Ant.
>> >> >They're quite old now and could use some updating.
>> >> >How do I go about contributing source to the Ant project?
>> >> >Do I need to send svn diff's to the mailing list, or is
>> >their another
>> >> >preferred way?
>> >>
>> >> I would suggest to deprecate the internal tasks and create a
>> >new antlib.
>> >>
>> >> Do you have some implementations?
>> >> I have written a new antlib for my company and I can ask for
>> >> contributing that.
>> >>
>> >>
>> >> Jan
>> >>
>> >> 
>-
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>
>> >>
>> >
>> >
>> >--
>> >"A lot of people are afraid of heights. Not me, I'm afraid 
>of widths."
>> >
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
>-- 
>"A lot of people are afraid of heights. Not me, I'm afraid of widt

Re: Updating the Continuous/Synergy tasks that are shipped with Ant

[Dave]

Well if you'd like to send me your Antlibs, I can do some testing for you
here. We're using Synergy 6.5 SP2 (and we're planning on installing the
first post-SP2 patch next wednesday). Would that be of interest to you?

On Fri, Nov 28, 2008 at 10:39 AM, <[EMAIL PROTECTED]> wrote:

> We are using Synergy 6.5 at the moment and using it since ... mmh ... 5.1?
> 4.5?
> With 6.5 Synergy has a Java client (ok present in 6.1 also), but sadly no
> real and open "API" so these tasks wrap the command line client.
>
> As often with scm tasks a test environment for unit tests is difficult ...
>
>
> Jan
>
>
>
>
>
>  initialRole=""/>
> Starts a Synergy session
>
> 
> Stops a Synergy session
>
> 
> Connects to a running session. ("CCM_ADDR" not set by the Java client any
> more)
>
> 
>
> 
> Check files out
>
> 
> Check a project out
>  ccm co -p ${project}-${version} -release ${release} -mod -path ${workarea}
>
> 
> Reconfigure command
>
>  asDefault=""/>
> Creates a new task
>
> 
>
>  interfacekind="info.interface"
> ip="info.ip"
> sessionid="info.session"
> user="info.user"
> computer="info.computer"/>
> 
> Gets information about the current session
>  [echoproperties] #Ant properties
>  [echoproperties] #Mon May 22 09:46:33 CEST 2006
>  [echoproperties] info.interface=Command Interface
>  [echoproperties] info.user=mat
>  [echoproperties] info.session=1707
>  [echoproperties] info.ip=130.11.36.89
>  [echoproperties] info.db=/rzf/db/skm/ccm_databases/uebungen
>  [echoproperties] info.computer=nb011689
>
> 
> 
>
>
>
> 
> Checks for a give role (task and condition)
>
> 
> Stores the object version of a given file in a property. Optional default
> value if not under CM control.
>
> 
>https://myJira.org/browse/
> "/>
> 
> Creates a changelist by getting all completed tasks of a release. The
> result is a text or xml file with release name and task synopsis. If
> "detailed" with their documentations too. A XSL could transform that into
> HTML.
> in="${build.dir}/changes-detailed.xml"
>out="${build.dir}/changes.html"
> >
>
>
>
>
> 
>
>
>
> 
> 
>
>
> 
> Moving with Synergy.
>
>
> 
> Checks whether an open Synergy session is available.
>
>
>
> >-Ursprüngliche Nachricht-
> >Von: Dave [mailto:[EMAIL PROTECTED]
> >Gesendet: Freitag, 28. November 2008 10:40
> >An: Ant Developers List
> >Betreff: Re: Updating the Continuous/Synergy tasks that are
> >shipped with Ant
> >
> >Sounds good. I haven't started working on them yet, but I'd probably be
> >enhancing the existing tasks a little (as they're still
> >relevant) and adding
> >one or two new tasks.I'll post back here once I have something to show.
> >Are you also using Synergy at your workplace, or was the antlib for
> >something else?
> >
> >On Fri, Nov 28, 2008 at 7:11 AM, <[EMAIL PROTECTED]> wrote:
> >
> >> >Hey all,
> >> >I'm the build manager working a financial company in Ireland.
> >> >I'd like to add some more functionality to the standard
> >> >Continuous/ Synergy
> >> >tasks which come with Ant.
> >> >They're quite old now and could use some updating.
> >> >How do I go about contributing source to the Ant project?
> >> >Do I need to send svn diff's to the mailing list, or is
> >their another
> >> >preferred way?
> >>
> >> I would suggest to deprecate the internal tasks and create a
> >new antlib.
> >>
> >> Do you have some implementations?
> >> I have written a new antlib for my company and I can ask for
> >> contributing that.
> >>
> >>
> >> Jan
> >>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> >
> >--
> >"A lot of people are afraid of heights. Not me, I'm afraid of widths."
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
"A lot of people are afraid of heights. Not me, I'm afraid of widths."

AW: Updating the Continuous/Synergy tasks that are shipped with Ant

[Jan.Materne]

We are using Synergy 6.5 at the moment and using it since ... mmh ... 5.1? 4.5?
With 6.5 Synergy has a Java client (ok present in 6.1 also), but sadly no real 
and open "API" so these tasks wrap the command line client.

As often with scm tasks a test environment for unit tests is difficult ...


Jan






Starts a Synergy session


Stops a Synergy session


Connects to a running session. ("CCM_ADDR" not set by the Java client any more)




Check files out


Check a project out
  ccm co -p ${project}-${version} -release ${release} -mod -path ${workarea}
  

Reconfigure command


Creates a new task





Gets information about the current session
  [echoproperties] #Ant properties
  [echoproperties] #Mon May 22 09:46:33 CEST 2006
  [echoproperties] info.interface=Command Interface
  [echoproperties] info.user=mat
  [echoproperties] info.session=1707
  [echoproperties] info.ip=130.11.36.89
  [echoproperties] info.db=/rzf/db/skm/ccm_databases/uebungen
  [echoproperties] info.computer=nb011689







Checks for a give role (task and condition)


Stores the object version of a given file in a property. Optional default value 
if not under CM control.


https://myJira.org/browse/"/>

Creates a changelist by getting all completed tasks of a release. The result is 
a text or xml file with release name and task synopsis. If "detailed" with 
their documentations too. A XSL could transform that into HTML.














Moving with Synergy.



Checks whether an open Synergy session is available.



>-Ursprüngliche Nachricht-
>Von: Dave [mailto:[EMAIL PROTECTED] 
>Gesendet: Freitag, 28. November 2008 10:40
>An: Ant Developers List
>Betreff: Re: Updating the Continuous/Synergy tasks that are 
>shipped with Ant
>
>Sounds good. I haven't started working on them yet, but I'd probably be
>enhancing the existing tasks a little (as they're still 
>relevant) and adding
>one or two new tasks.I'll post back here once I have something to show.
>Are you also using Synergy at your workplace, or was the antlib for
>something else?
>
>On Fri, Nov 28, 2008 at 7:11 AM, <[EMAIL PROTECTED]> wrote:
>
>> >Hey all,
>> >I'm the build manager working a financial company in Ireland.
>> >I'd like to add some more functionality to the standard
>> >Continuous/ Synergy
>> >tasks which come with Ant.
>> >They're quite old now and could use some updating.
>> >How do I go about contributing source to the Ant project?
>> >Do I need to send svn diff's to the mailing list, or is 
>their another
>> >preferred way?
>>
>> I would suggest to deprecate the internal tasks and create a 
>new antlib.
>>
>> Do you have some implementations?
>> I have written a new antlib for my company and I can ask for
>> contributing that.
>>
>>
>> Jan
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
>-- 
>"A lot of people are afraid of heights. Not me, I'm afraid of widths."
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] IvyDE 2.0.0.beta1 Release

[Erik-Berndt Scheper]

Seems like a good idea; although the beta was perfectly fine on my
machine (Eclipse 3.4.1).

Regards,

Erik-Berndt

On Thu, 2008-11-27 at 17:14 +0100, Nicolas Lalevée wrote:

> Thanks to some early testers on the ivy-user mailing list [1], they 
> spotted an incompatibility of the IvyDE updatesite  with RAD 7. The fix 
> is quite trivial: building the updatesite with java 5 more than java 6.
> Any objection to redo the release ?
> 
> Nicolas
> 
> [1] http://marc.info/?l=ivy-user&m=122779912328682&w=2
> 
> Nicolas Lalevée a écrit :
> > I have built a release candidate for IvyDE 2.0.0.beta1
> >
> > You can download the distribution from this URL: 
> > http://people.apache.org/~hibou/ivyde-2.0.0.beta1/ 
> > 
> >
> > And a staging update site has been setup there: 
> > http://people.apache.org/~hibou/staging/updatesite 
> > 
> >
> > Do you vote for the release of these binaries?
> >
> > [ ] Yes
> > [ ] No
> >
> > Regards,
> >
> > Nicolas, IvyDE 2.0.0.beta1 release manager
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Disclaimer:
This message contains information that may be privileged or confidential and is 
the property of Sogeti Nederland B.V. or its Group members. It is intended only 
for the person to whom it is addressed. If you are not the intended recipient, 
you are not authorized to read, print, retain, copy, disseminate, distribute, 
or use this message or any part thereof. If you receive this message in error, 
please notify the sender immediately and delete all copies of this message.

Re: Updating the Continuous/Synergy tasks that are shipped with Ant

[Dave]

Sounds good. I haven't started working on them yet, but I'd probably be
enhancing the existing tasks a little (as they're still relevant) and adding
one or two new tasks.I'll post back here once I have something to show.
Are you also using Synergy at your workplace, or was the antlib for
something else?

On Fri, Nov 28, 2008 at 7:11 AM, <[EMAIL PROTECTED]> wrote:

> >Hey all,
> >I'm the build manager working a financial company in Ireland.
> >I'd like to add some more functionality to the standard
> >Continuous/ Synergy
> >tasks which come with Ant.
> >They're quite old now and could use some updating.
> >How do I go about contributing source to the Ant project?
> >Do I need to send svn diff's to the mailing list, or is their another
> >preferred way?
>
> I would suggest to deprecate the internal tasks and create a new antlib.
>
> Do you have some implementations?
> I have written a new antlib for my company and I can ask for
> contributing that.
>
>
> Jan
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
"A lot of people are afraid of heights. Not me, I'm afraid of widths."

Re: [VOTE] IvyDE 2.0.0.beta1 Release

[Nicolas Lalevée]

Maarten Coene a écrit :

I'm getting an error when trying to update the already installed IvyDE plugin.
I'm using Eclipse 3.4.0 and tried both 
http://people.apache.org/~hibou/staging/updatesite and 
http://people.apache.org/~hibou/test-updatesite/

This is the information I could find in the Eclipse .log file

!ENTRY org.eclipse.equinox.p2.metadata.repository 2 0 2008-11-27 22:59:53.890
!MESSAGE Error parsing metadata repository
!SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-11-27 22:59:53.890
!MESSAGE Error at line 10, column 91: Missing required attribute in 
"repository": url
!SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-11-27 22:59:53.890
!MESSAGE Error at line 10, column 91: Illegal value for attribute "url" of element 
"repository": null
!SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-11-27 22:59:53.890
!MESSAGE Error at line 11, column 91: Missing required attribute in 
"repository": url
!SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-11-27 22:59:53.890
!MESSAGE Error at line 11, column 91: Illegal value for attribute "url" of element 
"repository": null
!SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-11-27 22:59:53.890
!MESSAGE Error at line 12, column 90: Missing required attribute in 
"repository": url
!SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-11-27 22:59:53.890
!MESSAGE Error at line 12, column 90: Illegal value for attribute "url" of element 
"repository": null
!SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-11-27 22:59:53.890
!MESSAGE Error at line 13, column 90: Missing required attribute in 
"repository": url
!SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-11-27 22:59:53.890
!MESSAGE Error at line 13, column 90: Illegal value for attribute "url" of element 
"repository": null

!ENTRY org.eclipse.equinox.p2.engine 4 4 2008-11-27 23:00:22.142
!MESSAGE An error occurred during provisioning.
!SUBENTRY 1 org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2008-11-27 
23:00:22.142
!MESSAGE Failed to prepare partial IU: [R]org.apache.ivy 2.0.0.cr2.
  


I downloaded a fresh eclipse 3.4 for linux, installed the IvyDE alpha1 
from the official updatesite.
Then I setup the staging updatesite, make Eclipse update my plugins. 
Every thing worked fine for me, the IvyDE test projects are resolved 
correctly.

I googled a little bit your error, I didn't found anything interesting...
It just make me think of when my Eclipse was somehow fucked up because I 
tried to update to Ivy RC2 while it has not been deployed yet on the 
apache mirrors (due to some propagation time). Eclipse just never 
accomplished to see that Ivy RC2 was there, even a week after the 
release... I had to reinstall my Eclipse...



Nicolas




Maarten




- Original Message 
From: Nicolas Lalevée <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Thursday, November 27, 2008 11:04:34 AM
Subject: [VOTE] IvyDE 2.0.0.beta1 Release

I have built a release candidate for IvyDE 2.0.0.beta1

You can download the distribution from this URL: 
http://people.apache.org/~hibou/ivyde-2.0.0.beta1/ 


And a staging update site has been setup there: 
http://people.apache.org/~hibou/staging/updatesite 


Do you vote for the release of these binaries?

[ ] Yes
[ ] No

Regards,

Nicolas, IvyDE 2.0.0.beta1 release manager


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]