correctly.
For my problem I turned off the index attribute in the jar task.
Thanks, I will close the bug -
https://issues.apache.org/bugzilla/show_bug.cgi?id=47446 as INVALID.
Regards,
Garima.
On Wed, Jul 1, 2009 at 9:24 AM, Steve Loughran wrote:
> Garima Bathla wrote:
>
&g
he length 72. If your jar file name is getting splitted because of
> this
> length limit, add extra spaces (which is file according to the specs) until
> the 72nd character. Add your jar file name thereafter. This would not cause
> splits within your file names.
>
> I am curious to kn
wrote:
> Just curious: Why don't you use the task and the
> task?
>
> On Mon, Jun 29, 2009 at 3:02 AM, Garima Bathla
> wrote:
> > Dear Fellow memebers,
> >
> > I really need help , I have been stuck with same problem for few days
> now.
> >
> >
Dear Fellow memebers,
I really need help , I have been stuck with same problem for few days now.
Problem:
As we all know, manifest file syntax is very sensitive ( sensitive to
spaces, # of characters in a line, \n character). And I have learn it very
hard way that if Class-Path in a jar is not se
t;, "ModuleName", "Revision"));
Configuration[] con = rmd.getDescriptor().getConfigurations();
String[] confs2 = rmd.getDescriptor().getConfigurationsNames();
Regards,
Garima.
On Fri, Mar 27, 2009 at 1:10 PM, Garima Bathla wrote:
> My requirement i
It does makes sense
>From the error :
configurations={core=core, stax=stax, xpp3=xpp3, woodstox=woodstox}
You only have above configurations available but somewhere in some
dependency you are referring to default conf which does not exist.
On Tue, Feb 10, 2009 at 12:05 PM, Buck, Robert wrote:
