Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[discussion] very few dependencies rely on terracottas nexus #279

Closed
jarlah opened this issue Nov 14, 2018 · 8 comments
Closed

[discussion] very few dependencies rely on terracottas nexus #279

jarlah opened this issue Nov 14, 2018 · 8 comments
Labels
stale Inactive items that will be automatically closed if not resurrected

Comments

@jarlah
Copy link

jarlah commented Nov 14, 2018

There are actually a few couple of dependencies that does not exist in central. But they seem to be test related.

@jarlah jarlah changed the title [discussion] very few dependencies rely on terracotta repo [discussion] very few dependencies rely on terracottas nexus Nov 14, 2018
@zemian
Copy link
Contributor

zemian commented Nov 14, 2018

Can you help identify which dependency this is?

On a related note, I know there is odd maven plugin that still requires "svn" executable to be in path in order to build. This we should remove as well. See #66

@jarlah
Copy link
Author

jarlah commented Nov 14, 2018

    <dependency>
      <groupId>org.terracotta</groupId>
      <artifactId>product-upgradability-testing-utils</artifactId>
      <version>0.9.0</version>
      <scope>test</scope>
    </dependency>

and

      <plugin>
        <groupId>org.terracotta</groupId>
        <artifactId>maven-forge-plugin</artifactId>
        <version>${maven-forge-plugin.version}</version>
      </plugin>

@jarlah
Copy link
Author

jarlah commented Nov 14, 2018

at least these two. Will continue to investigate.

@zemian
Copy link
Contributor

zemian commented Dec 20, 2018

I have now cleaned up 'maven-forge-plugin' that affect normal build process. If you try master branch with "./mvnw clean package", it should build successful.

As for the 'product-upgradability-testing-utils' it is only for testing, and I am not familiar with it enough to make judgement on remove or replace.

@jarlah
Copy link
Author

jarlah commented Dec 21, 2018

When i saw you committed to master i was like. Dude. You couldn't have told me earlier that you have push access? ;) but Great. Nice to see that there is hope in this project. However i will not leave you alone. If we can find some tasks to improve on or plan, i can try to work on them and contribute in this way.

@jarlah
Copy link
Author

jarlah commented Dec 21, 2018

The whole reason why i was making a fork was that the project was seamingly umaintanable. Now that you have pushed to master i will happily delete all plans to fork or clone or do anything experimental.

@zemian
Copy link
Contributor

zemian commented Dec 29, 2018

@jarlah, well, no commit direct to master, but merge only. Yes I have accept merge permission access.

Best way to help is try go through all the existing issues and PRs and clear them out. I have cleanup the labels so hopefully it can make issues easier to classify.

@stale
Copy link

stale bot commented Aug 3, 2021

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale Inactive items that will be automatically closed if not resurrected label Aug 3, 2021
@jarlah jarlah closed this as completed Aug 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Inactive items that will be automatically closed if not resurrected
Projects
None yet
Development

No branches or pull requests

2 participants