I had a solution for this problem using @Named, but i had trouble getting
it to work, I probably did something wrong. I'll give it one more shot.
Just move the issue along if I don't fix it by the time you cut the release.
Kristian
2014-01-28 Jason van Zyl
> There are only a few issues left w
There are only a few issues left which Igor and I will close out over the next
couple days.
Kristian, there's one issue left in the pile that's assigned to you. If you
don't have time to look at it can you please move it to the 4.x pile.
Thanks,
Jason
On Jan 27, 2014, at 3:35 PM, Gary O'Neall wrote:
> Hi Jason,
>
> Thanks for the response and suggestions.
>
> Currently, the plugin is only taking information from the POM and formatting
> it as an SPDX file.
>
> With the plugin, I am primarily targeting developers and organization which
> or
Github user mfriedenhagen closed the pull request at:
https://github.com/apache/maven-enforcer/pull/12
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hi Jason,
Thanks for the response and suggestions.
Currently, the plugin is only taking information from the POM and formatting
it as an SPDX file.
With the plugin, I am primarily targeting developers and organization which
originate the code. In this case, the license information in the POM is
GitHub user mfriedenhagen opened a pull request:
https://github.com/apache/maven-enforcer/pull/12
MENFORCER-182: document the changes of MENFORCER-160.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mfriedenhagen/maven-enforcer
Github user mfriedenhagen closed the pull request at:
https://github.com/apache/maven-enforcer/pull/10
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Github user mfriedenhagen closed the pull request at:
https://github.com/apache/maven-enforcer/pull/11
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Gary,
Does the plugin do any source level scanning to determine licenses, or are you
just taking the information from the POM? If you're using something like
JNinka[1] to figure out what licenses are actually present then that's a first
step. Actually determining if it's a valid set of licenses
> This problem is specific to maven-plugin-testing-harness. You can use
> any version of Guava at runtime, but test classpath is flat so you need
> to use single Guava version that is compatible with all components.
>
> Unfortunately, I don't know how to fix the problem, at least not until
> Maven
10 matches
Mail list logo
