Maven 2.x Build Helper Plugin

Using an artifacts filename (without extension) as the default classifier

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 1.7
  • Fix Version/s: None
  • Labels:
    None
  • Environment:
    Ubuntu.
  • Number of attachments :
    0

Description

Recently I needed to use the build helper to make twenty xsd files into artifacts. This required that I make twenty entries into the artifacts as there was no neat way to say, all the files in directory X.

As I had twenty files all of the same type I was requried to give them a classifier, I couldnt think of anything acccept the xsd files name without the extension, I think that this would useful behaviour, either as the default or that can be turned on as part of the configuration.

It would also have the effect that it would allow for the use of artifact sets that could make use of the include and exclude behaviour.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Baptiste Mathus added a comment - - edited

Hi,
Could you please indicate which goal you're refering to, and maybe provide a test project to be able to both reproduce your issue and better understand it?

Thanks

Show
Baptiste Mathus added a comment - - edited Hi, Could you please indicate which goal you're refering to, and maybe provide a test project to be able to both reproduce your issue and better understand it? Thanks
Hide
Permalink
Gavin Tranter added a comment -

Wow, this is from way back. Our build system has changed a lot since then, but I will have a look see if we still have the pons.

From memory, we had a bunch of xsd files in a directory and we wanted the build helper plugin to export them as artefacts, and we wanted the artefacts to have the same name as the xsd's. I think the problem was I had to configure it to have each xsd's filename actuall in the pom because i couldn't use the normal method of configuring maven to include/exclude things in a named directory, and have the plugin just use the filename and extension as the artefact name.

Will see if I can grab examples from our poms, they should at least be in the source repos history.

Show
Gavin Tranter added a comment - Wow, this is from way back. Our build system has changed a lot since then, but I will have a look see if we still have the pons. From memory, we had a bunch of xsd files in a directory and we wanted the build helper plugin to export them as artefacts, and we wanted the artefacts to have the same name as the xsd's. I think the problem was I had to configure it to have each xsd's filename actuall in the pom because i couldn't use the normal method of configuring maven to include/exclude things in a named directory, and have the plugin just use the filename and extension as the artefact name. Will see if I can grab examples from our poms, they should at least be in the source repos history.

People

  • Assignee:
    Unassigned
    Reporter:
    Gavin Tranter
Vote (0)
Watch (2)

Dates

  • Created:
    Updated: