Just keep in mind, that overriding the finalName only works for adjusting
the local file name when it's not attached to the build (in addition to the
directory name in an assembly). The final name is not used when it is
deployed to a Maven server or installed to the local repository. In those
cases
Overriding the finalName is what I was assuming I'd need to change, but
thanks for the extra context, Christopher.
At least I know where I can look if I find the time to try to fix this
for the next sucker.. I mean release manager ;)
Christopher wrote:
I think we also had to override the fin
I think we also had to override the finalName in the root execution of
maven-assembly-plugin, so unpacking the source tarball wouldn't have a
directory called "accumulo-project-", and instead would look like
"accumulo-".
On Fri, May 20, 2016 at 2:29 PM Christopher wrote:
> We had a similar probl
We had a similar problem in Accumulo. We wanted the artifact ID of our
tarballs to just be "accumulo". So our parent pom is now called
"accumulo-project", and one of the modules (that creates the tarballs) is
called just "accumulo".
This works for our -bin tarball (classifier: "bin" in the assembl
FWIW, Fedora (and CentOS 7) now has xmvn for building jars using maven, but
which resolves maven deps using locally installed RPMs. In fact, CentOS 7
has better support for maven builds this way than it does for ant builds. I
can only speak about Fedora/CentOS stuff, because that's what I use and
c
On 20 May 2016 at 18:26, Gary Gregory wrote:
> On Fri, May 20, 2016 at 10:22 AM, sebb wrote:
>
>> On 20 May 2016 at 18:09, Gary Gregory wrote:
>> > I've seen some projects that run checkstyle early in the build and causes
>> > the build to fail if there are violations.
>> >
>> > That seems like
On Fri, May 20, 2016 at 10:22 AM, sebb wrote:
> On 20 May 2016 at 18:09, Gary Gregory wrote:
> > I've seen some projects that run checkstyle early in the build and causes
> > the build to fail if there are violations.
> >
> > That seems like a nice way to avoid piling up violations over time, an
On 20 May 2016 at 18:09, Gary Gregory wrote:
> I've seen some projects that run checkstyle early in the build and causes
> the build to fail if there are violations.
>
> That seems like a nice way to avoid piling up violations over time, and
> then spending time fixing them which is boring.
>
> I
On Fri, May 20, 2016 at 10:13 AM, sebb wrote:
> On 20 May 2016 at 18:05, Gary Gregory wrote:
> > Hi,
> >
> > Can't the shade plugin could do the pruning with its minimize feature?
>
> It's more than just a prune; the manifest also needs to be updated
> with the main class.
>
> But if you want to
On 20 May 2016 at 18:05, Gary Gregory wrote:
> Hi,
>
> Can't the shade plugin could do the pruning with its minimize feature?
It's more than just a prune; the manifest also needs to be updated
with the main class.
But if you want to try it, go ahead.
Note that you would still need much of the a
Fine with me but don't we get push back from some Linux distro folks that
use Ant to build jars for their distros?
This should be JIRA'd IMO.
Gary
On Fri, May 20, 2016 at 6:08 AM, wrote:
> Author: sebb
> Date: Fri May 20 13:08:42 2016
> New Revision: 1744732
>
> URL: http://svn.apache.org/view
I've seen some projects that run checkstyle early in the build and causes
the build to fail if there are violations.
That seems like a nice way to avoid piling up violations over time, and
then spending time fixing them which is boring.
I think we should do that.
Thoughts?
Gary
On Fri, May 20,
Hi,
Can't the shade plugin could do the pruning with its minimize feature?
Gary
-- Forwarded message --
From:
Date: Fri, May 20, 2016 at 4:42 AM
Subject: svn commit: r1744720 - /commons/proper/codec/trunk/pom.xml
To: comm...@commons.apache.org
Author: sebb
Date: Fri May 20 11:
On 20 May 2016 at 15:39, Josh Elser wrote:
>
>
> Benedikt Ritter wrote:
>>
>> Hello Josh,
>>
>> Josh Elser schrieb am Fr., 20. Mai 2016 um 05:28 Uhr:
>>
>>> > One more (final?) snafu: turns out I used the "wrong" name for the
>>> > artifacts in dist.a.o which caused the website to have the wron
The Apache Commons team is pleased to announce the release of Apache
Commons VFS 2.1. Apache Commons VFS provides a single API for accessing
various different file systems. It presents a uniform view of the files
from various different sources, such as the files on local disk, on an
HTTP server
Benedikt Ritter wrote:
Hello Josh,
Josh Elser schrieb am Fr., 20. Mai 2016 um 05:28 Uhr:
> One more (final?) snafu: turns out I used the "wrong" name for the
> artifacts in dist.a.o which caused the website to have the wrong links.
>
> Just corrected that, sadly the website will continue
Hello Robert,
Robert Huffman schrieb am Do., 19. Mai 2016 um
17:00 Uhr:
> Thanks for the comments. Yes, it is in progress.
>
> I generally keep imports collapsed and never look at them. I hadn't even
> realized that was the style here. Thanks for pointing it out.
>
> I already changed ITERABLE t
On 20 May 2016 at 08:53, Benedikt Ritter wrote:
> b. "Open Cryptographic Interface" items. [740.17(b)(2)]
> looks correct. But this is just my lucky guess.
I'm struggling to find the official definition of "OCI", but I think it's this:
https://www.bis.doc.gov/index.php/forms-documents/doc_view/
18 matches
Mail list logo
