Use the standard compile plugin by default #109
Conversation
This will now only used the forked version of the plugin if a profile has been activated that uses additionalClasspathElements.
|
@dmlloyd who usually merges and releases this project? I think I technically have permissions, but I have not done it before. |
|
Sorry, I missed this in my email. I think @jamezp did the last few. I've done tags in the past but "the old way" (releasing through repository.jboss.org and not making a GitHub release) which might or might not still be okay. |
|
I've merged it. I've never done a release, but I assume it's just a standard release so I can if needed. It's been nearly 1.5 years since 38 was released so we're likely due :) |
|
Sorry, I just went off the fact that your name was on the tag. I wonder if we want to start moving projects like this one towards releasing directly to central. It's possible to configure GitHub to do the work for us (that's what SmallRye does). |
|
No worries. I don't think anyone really "owns" it. If you've got instructions on how to do that I'm all game. I tried to do it for a RESTEasy project and need proof I owned jboss.org. |
|
If it is just released through JBoss Nexus then I can do it if needed. That is not going to be a long term solution though. |
|
Either way works. I'm happy to do it or feel free. I'm not sure how we're going to handle this in the future. |
This will now only used the forked version of the plugin if a profile
has been activated that uses additionalClasspathElements.